ckan_discover_datasets

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

Annotations already declare readOnlyHint:true, but the description adds valuable behavioral context: it is keyless, returns specific fields like resourceId and datastoreActive, warns that datastoreActive:false resources are raw file blobs not in the datastore, and mentions the totalAvailable count. No contradictions with 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?

The description is concise yet packed with all necessary information: purpose, inputs with examples, output format, and usage guidance. Each sentence serves a distinct purpose, and critical details are front-loaded. No extraneous content.

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's complexity (3 parameters, no output schema), the description fully covers what the tool does, how to use it, and what the returned data means (including datastoreActive flag). It provides enough context for an agent to correctly invoke the tool and interpret results without additional documentation.

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?

With 100% schema description coverage, baseline is 3. The description adds extra value beyond the schema by providing example values for q (e.g., 'procurement'), clarifying the enum meanings for host (allowlisted .gov portals), and specifying the limit default (20) and maximum (100). It also notes 'keyless' operation, which is not in the schema.

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 action: 'Find CKAN datastore resource ids by keyword via package_search (keyless).' It distinguishes itself from the sibling tool ckan_query by indicating that results should be fed to ckan_query for actual data querying. Also, specific host enums and example keywords like 'procurement' and 'checkbook' make the purpose unambiguous.

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 provides explicit input instructions for host, q, and limit, and advises to feed a datastoreActive:true result's resourceId to ckan_query. It implies when to use this tool (to discover datasets) and how to proceed, but does not explicitly compare with other sibling tools like socrata_discover_datasets. However, the guidance is sufficient for proper usage.

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