datosgob_cercar_datasets

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

No annotations are present, so the description carries the full burden. It describes the basic search operation but does not disclose external API dependency, rate limits, authentication, idempotency, or data freshness. The mention of dataset count is factual but not behavioral.

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 with only three sentences, front-loaded with the action. It efficiently communicates the purpose, but could be slightly more structured (e.g., separate usage context).

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 6 optional parameters and an output schema, the description is minimal. It does not mention pagination behavior despite page/page_size parameters, nor does it describe the result structure. The output schema likely covers return values, so completeness is adequate but lacks some contextual details.

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%, so the baseline is 3. The description adds no additional parameter meaning beyond what is already in the input schema descriptions. It provides a general context but no extra details.

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 datasets in the national open data catalog (verb 'cerca', resource 'datasets', specific catalog). It mentions available topics and dataset count, distinguishing it from other search tools by being specific to datos.gob.es. However, it does not explicitly contrast with sibling search 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?

No guidance is provided on when to use this tool versus other 'cercar' siblings (e.g., cercar_contractes, cercar_subvencions). There are no examples, prerequisites, or exclusions mentioned.

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