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

Annotations already declare readOnlyHint=true, so the description adds value by specifying the returned fields (titles, descriptions, modality, etc.) and the deprecation status. It does not contradict 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: the first clearly flags deprecation and alternative, the second concisely states the tool's function and return fields. No extraneous information.

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?

Given the tool is deprecated and has 9 optional parameters (no output schema), the description adequately covers its purpose, return fields, and deprecation. It could be more complete, but it is sufficient for its deprecated status.

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?

The description does not add semantic meaning beyond the input schema; it only states what is returned. With schema description coverage at 56%, the baseline is 3, and the description provides no additional parameter guidance.

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 it lists datasets in a catalogue and explicitly mentions deprecation and the alternative (search_catalog). The verb 'List' and resource 'datasets' are specific, and the mention of a sibling tool distinguishes it.

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 'Deprecated: use search_catalog (kind=dataset); this tool will be removed in a future release', providing clear guidance on when not to use it and what alternative to use.

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