Listar datasets de SUNAT

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

No annotations are provided, so the description carries the burden. It states the tool lists datasets but does not disclose behavioral traits like rate limits, pagination (since no params, likely all results at once), or the exact structure of each result beyond the 'dataset' field.

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?

Two sentences with no wasted words. The first sentence states the purpose, and the second provides usage guidance. Front-loaded and efficient.

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 no parameters and no output schema, the description is fairly complete: it specifies the data source, gives examples, and links to the next tool. However, it could describe the output format more fully, though the sibling tool reference compensates.

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?

There are no parameters, so schema coverage is 100%. The description adds value by explaining how to use the output (the 'dataset' field) with another tool, which is beyond 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 tool lists SUNAT datasets, provides examples (padrones, comprobantes), and specifies the source platform (datosabiertos.gob.pe). It distinguishes from sibling tools by indicating how to use the output with sunat_obtener_dataset.

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 tells when to use the tool (to list datasets) and directs the agent to use the 'dataset' field with sunat_obtener_dataset for resources. However, it does not explicitly exclude other use cases or compare with siblings beyond the next step.

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