Extraer informacion de Bodegas

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds that the tool generates an .xlsx file and returns the first rows parsed, which is important side-effect and output-format context beyond the 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 short sentences, totaling about 20 words. It states the purpose first and the behavior second without redundant filler.

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?

Given the 13-parameter schema with complete descriptions and annotations that cover the read-only nature, the description adequately covers the core behavior: generating an xlsx and returning a preview. It does not detail the contents of the rows, but the schema and tool name provide sufficient context for the agent.

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 has 100% coverage, documenting all 13 parameters including ranges and defaults. The description provides no additional parameter semantics, so the baseline of 3 applies since the schema already carries the meaning.

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 states 'Extraer informacion de Bodegas (funcion GETTBO de SIIGO Pyme)' which clearly identifies the action (extract warehouse info) and the specific SIIGO function. It adds that it generates an .xlsx and returns parsed rows, but does not explicitly differentiate from sibling tools like siigo_getbod or siigo_getbop that may also relate to warehouses.

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?

Usage is implied by the purpose: one would use this to extract warehouse information from SIIGO. However, there is no explicit guidance on when to choose this over alternative bodega-related tools or any exclusions, so it's left to the agent to infer.

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