holded_list_documents

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the basic listing/filtering behavior, but does not mention pagination, default ordering, response format, permission requirements, or any limits. This is a read operation by implication, but that is not explicit.

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 concise sentence that front-loads the core purpose and then mentions optional filters. It wastes no words, though it is brief enough that some behavioral details are omitted.

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 has 6 parameters, no output schema, and no annotations, yet the description only summarizes the input filtering behavior. It does not describe the return structure, pagination behavior, default sort, or other details an agent would need to confidently interpret the result of a list operation.

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 description coverage is 100%, so the schema already documents every parameter. The description adds only a general paraphrase of the date-range and contact filters, without providing additional semantics or clarifying the paid and sort parameters beyond what the schema already states.

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 clear verb ('Lista') and resource ('documentos de facturación de Holded') with a scoping qualifier ('por tipo'). It is distinguished from sibling list tools by being specific to documents, and from holded_get_document by listing instead of fetching a single document.

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 implies when to use the tool: when listing Holded billing documents by type, optionally filtered by date range or contact. However, it does not explicitly state when not to use it or mention alternatives such as holded_get_document for retrieving a single document.

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