Información de documento firmado

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context: it returns metadata and explicitly states it does not download the content, which clarifies the scope beyond the annotations. It does not cover auth or error behavior, but that is acceptable given the simple read-only nature.

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 short sentences, front-loaded with the main action and followed by a clear exclusion. Every sentence earns its place with no wasted words.

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?

The tool is simple with one parameter, an output schema exists, and annotations cover safety. The description sufficiently explains what it does, what it does not do, and the required token. No additional behavioral details are needed for a metadata lookup tool.

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 s567 parameter already has a description in the schema ('Token del documento extraído de hechos/sanciones/resoluciones'). The tool description mentions the token and document categories but does not add substantial new meaning beyond the schema. Baseline 3 applies given high schema coverage.

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 returns metadata for a signed CMF document using a specific verb ('Devuelve') and identifies the resource types (hechos, sanciones, resoluciones, informes). It also explicitly notes it does not download content, distinguishing it from sibling download tools.

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 clear context for use: you need a token s567 and you get metadata, not content. The negative statement 'No descarga el contenido' implies when not to use this tool, but it does not explicitly name alternative tools such as cmf_documento_descargar, so an explicit alternative reference is missing.

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