search_datasets

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

The description adds context that the tool returns summarized metadata (title, organization, formats, URL), which goes beyond the annotation 'readOnlyHint'. However, it does not disclose pagination behavior, potential rate limits, or the extent of data freshness. The annotation already indicates a safe read operation, so the description provides moderate additional transparency.

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 two concise sentences in Spanish, efficiently front-loaded with the primary action and resource in the first sentence. Every word serves a purpose with no 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?

Given the tool has six parameters (none required), no output schema, and annotations indicating read-only and open-world behavior, the description adequately covers the source, filters, and return fields. It could mention pagination (handled via limit/offset) but is otherwise sufficient for a search 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?

With 100% schema coverage, the schema already documents all six parameters with clear descriptions and examples. The main description only reiterates the filter dimensions (keyword, organization, tag, group) without adding new semantic information, so it meets 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 verb 'Busca datasets' and the resource 'datos.gob.do', with specific filter dimensions (keyword, organization, tag, group). It distinguishes from siblings like 'search_resources' by focusing on datasets and summary metadata.

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 implies usage for searching public datasets in the Dominican Republic open data portal, but does not explicitly state when to use this tool versus alternatives like 'search_resources' or 'list_recent_datasets'. No exclusions or prerequisites are mentioned.

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