Obtener metadata y URL de descarga real de un recurso

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

No annotations are provided, so the description bears full responsibility. It adds important behavioral context by noting that the 'formato' field is unreliable and that CSV files may actually be ZIP archives. It could mention authentication or rate limits, but the added detail is valuable.

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, no filler, efficiently conveys all necessary information. Every word has purpose.

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?

Without an output schema, the description summarizes the return value (metadata and download URL). It could list example fields, but for a single-parameter retrieval tool, the given detail is sufficient.

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% and the description does not add new information beyond what the parameter description already says ('Id del recurso, obtenido de sunat_obtener_dataset'). Baseline score applies.

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's purpose: given a resource id, it returns full metadata and the download URL. It explicitly references its predecessor (sunat_obtener_dataset), distinguishing it from siblings that handle datasets or previews.

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 indicates that the input comes from sunat_obtener_dataset, providing clear context. It includes a warning about the unreliable 'formato' field, but does not explicitly state when not to use or list alternatives.

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