Descargar documento firmado

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

Beyond the annotations (readOnlyHint, destructiveHint), the description adds security context: 'El servidor gestiona el token; nunca se expone al modelo.' This discloses token handling behavior and implies a safe download path. The large-doc suggestion also hints at potential size limits. No contradiction with annotations.

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 sentences, front-loaded with the primary action, and every sentence adds value: purpose, formats, security note, and an alternative for large documents. No redundancy or fluff.

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 one-parameter download tool with an output schema and readOnly annotations, the description covers the essential context: what it downloads, the token, server-side security, and a size-based fallback. It could mention error scenarios or supported formats in more detail, but overall it is sufficiently complete.

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?

The schema already describes s567 as 'Token del documento' (100% coverage), but the tool description enriches it by stating 'su token s567' and clarifying that the server manages it securely, adding meaning about the token's role in downloading signed documents.

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 ('Descarga un documento firmado'), the resource (CMF), and the formats (PDF/XLS/XLSX). It distinguishes itself from sibling tools like cmf_documento_info and cmf_documento_markdown by specifying the signed document token usage.

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 provides an explicit alternative for large documents ('Para documentos grandes use el resource cmf://documento/{id}'), telling the agent when not to use this tool. It could additionally mention when to prefer cmf_documento_markdown for markdown conversion, but the large-doc guidance is clear.

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