holded_get_document

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

No annotations are provided, so the description carries the burden. 'Obtiene el detalle' clearly signals a read/retrieval operation, which is the core behavior. However, it does not disclose response format, error behavior, permissions, or any other behavioral context beyond the basic fetch.

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 a single, front-loaded sentence that immediately states the action and the key qualifiers. There is no filler or redundant information, making it appropriately concise for a simple two-parameter tool.

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 getter, the description provides enough to select and invoke the tool correctly given the complete schema. However, with no output schema and no annotations, it does not clarify what the returned 'detalle' includes or how errors are handled, leaving a moderate completeness gap.

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 input schema already documents both parameters fully, including an enum for docType and descriptions for both fields (100% coverage). The description only restates 'por su tipo e ID' and adds no additional meaning about parameter values, formats, or relationships.

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 uses a specific verb ('Obtiene') and clearly identifies the resource: a specific Holded document filtered by type and ID. This distinguishes it from list-oriented siblings like holded_list_documents, though it does not explicitly name the alternative.

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 phrase 'documento específico' implies the tool is for retrieving a single known document rather than listing documents, but there is no explicit guidance on when to use it versus alternatives or what prerequisites apply. Usage context is implied, not stated.

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