Extraer Terceros

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds that the tool generates an .xlsx file and returns parsed first rows, which is a useful side-effect context beyond the annotations. However, it doesn't disclose other behaviors such as credential requirements or potential delays.

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 communicates purpose and output behavior without redundancy. It conveys the essential information efficiently.

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 tool with 14 parameters and a file-generation side effect, the description gives only a high-level overview. The detailed schema compensates significantly, but the description could benefit from explaining what 'Terceros' represents and any prerequisites such as SIIGO installation or credentials.

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 has 100% description coverage for all 14 parameters, so the description adds little parameter-level meaning. It relates to the filasPreview parameter by mentioning 'first rows' but not explicitly. The baseline of 3 applies since the schema carries the parameter semantics.

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 verb ('Extraer'/'extract') and resource ('Terceros'/'third parties'), and clarifies it is a GETTER that generates an .xlsx and returns parsed rows. This distinguishes it from many sibling getters by naming a specific entity, though it doesn't explicitly contrast with alternatives.

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 offers no guidance on when to use this tool versus alternatives like siigo_pushter or other getter tools. The only usage hint appears in a schema parameter description (referencing siigo_list_companies), not in the tool description itself.

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