Buscar datasets en el portal de datos abiertos

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

Annotations already declare readOnlyHint, openWorldHint and non-destructive behavior, so the safety profile is covered. The description adds the default source (national portal) and the browse semantics of sort="recent", but says nothing about pagination, result limits or cross-portal behavior that would enrich the picture.

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?

Three tight sentences, front-loaded with the core action, followed by a concrete usage tip and the next-step tool. No filler or 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?

With an output schema covering return values and annotations covering safety, the description supplies the remaining essentials: default portal and the recent-browse workflow. It is complete enough to call the tool correctly, missing only minor detail on pagination behavior across pages.

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 100%, so the schema already documents all seven parameters including defaults and enum meanings. The description restates the default source and the sort="recent" behavior, adding only minimal value beyond the schema, so the baseline 3 holds.

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?

States a specific verb (Search) and resource (CKAN open-data datasets), and names the downstream tool (list_dataset_resources). The mention of the CKAN resource type differentiates it reasonably from generic siblings, though it never explicitly contrasts with other search_* tools like search_organizations.

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?

Gives an explicit usage pattern: use sort="recent" without a query to browse new/updated datasets, and points to the natural next step (list_dataset_resources). It lacks an explicit when-not-to-use or a named alternative sibling, but the context is clear.

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