search_datasets

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

Annotations already provide readOnlyHint=true and destructiveHint=false, so safety is clear. The description adds valuable behavioral details: results include portal-prefixed IDs, searches fan out to all portals by default, and the portal param narrows scope. It does not mention pagination or performance limits, but given the output schema exists, this is acceptable.

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?

The description is well-structured, starting with the primary action, then result format and workflow, then parameter explanations in a clean list. Every sentence adds value, and there is no redundancy or fluff.

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 output schema exists and annotations are present, the description covers all critical context: purpose, result unit, workflow integration, default behavior, and all parameter semantics. It is complete for an AI agent to correctly select and invoke the tool.

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 description coverage is 0%, so the description must compensate fully. It provides meaningful descriptions for all 7 parameters, including allowed values (e.g., 'CSV', 'JSON') and clarifications like limit being per portal (1-50). This exceeds what the bare schema offers.

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 searches for datasets across three named open data portals, providing a specific verb and resource. It distinguishes itself from sibling tools like get_dataset_info and download_resource by explaining how the results (portal-prefixed IDs) are used in subsequent steps.

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 guides when to use this tool (searching), how to use the results (with get_dataset_info, download_resource, get_resource_schema), and when to narrow with the portal param. It also indicates default behavior and provides workflow context, leaving no ambiguity about usage.

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