Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds value by stating there is no datastore and that agents must fetch resources[].download_url or url for the data. This adds behavioral context beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences only. The first explains the tool's purpose and mentions CKAN, the second gives usage and data handling advice. No unnecessary words or redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description explains what is returned (full metadata, download URLs) and how to use the data (no datastore, fetch download_url). It also references the search_datasets tool for input. This is complete for a simple one-parameter, read-only tool with rich annotations.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with the schema describing the 'id' parameter. The description adds that the id comes from search_datasets, which provides additional semantic meaning and connects to a sibling tool, raising the value beyond the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves full metadata for one dataset, including resources and download URLs. It explicitly mentions CKAN package_show, which is a specific verb-resource combination. It distinguishes from sibling tools like search_datasets (which returns a list) and from other data-access tools.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly says to use a dataset name/slug or id from search_datasets, providing clear context for when this tool should be invoked. It does not state when not to use it, but the instruction implies it's for individual dataset details after a search, which is sufficient guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.