download_edition_by_number

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

The description discloses the return format ('metadata plus the saved file path and size') and error behavior ('Raises if the edition number is not found'), which is helpful. However, it does not discuss side effects (e.g., file system writes, overwrite behavior) or safety, and relies on a cross-reference for output_dir details. With no annotations, this is adequate but not comprehensive.

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, front-loads the main purpose, and separates parameter details. It uses clear formatting. One sentence on output_dir references another tool, which is efficient but somewhat indirect.

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?

For a simple tool with two parameters and no output schema or annotations, the description covers the core purpose, parameters with examples, return value, and error behavior. It is mostly complete, though it omits details on output_dir default behavior (e.g., when null) and file naming.

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 0% schema description coverage, the description compensates by providing examples for the 'number' parameter ('e.g., "53524" or "53.524"') and a cross-reference for 'output_dir'. This adds practical meaning beyond the bare schema types.

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 action ('Download') and the resource ('a specific Diario Oficial edition by its edition number'). It differentiates from sibling tools through the parameter, but does not explicitly contrast with download_edition_by_date.

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 its siblings (e.g., download_edition_by_date or download_latest_edition). There is no mention of context or alternatives.

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