[man-shar]

The plugin's description of describe_dataset now says that release dates are returned only when the dataset metadata supplies them, can be absent or out of date, and must be verified with the publisher. The wording matches the tool description the FactIQ server emits. Both plugin versions increase from 0.37.0 to 0.37.1.

The problem

The tool table in the skill and the eval mock tool listing described describe_dataset as returning "release dates". The server includes last_release_date and next_release_date only when a dataset's stored metadata has them, and a stored date is not a live release calendar. An agent reading the old wording could treat a missing or stale date as the current release status.

The fix

Same input: the describe_dataset row in the tool table of skills/factiq/SKILL.md.

Before:

Full metadata for one dataset: topic, methodology, release dates, base-change notice, dimensions, example series. Call after `search_datasets`.

After:

Full metadata for one dataset: topic, methodology, base-change notice, dimensions, example series. Last/next release dates appear only when the dataset metadata supplies them and can be absent or out of date; verify the current or upcoming release with the publisher. Call after `search_datasets`.

The describe_dataset entry in evals/mocks/factiq/_tools.json gets the server's emitted description text. Other tool entries and all mock result values are unchanged. The existing freshness guidance in the SQL guide already sends the agent to the publisher's official page for current and upcoming releases; this change only stops the tool description from suggesting the dates are always present and current.

Validation

The existing plugin suite passes: 73 tests. Both version files contain 0.37.1, above 0.37.0 on main. The mock description was compared with the server's emitted describe_dataset description and is identical.