sii_convenios_internacionales

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the queryable dimensions (country, subject, related document) but no further behavioral context such as result format or coverage limits. Adequate given the annotation coverage.

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?

A single front-loaded sentence that names the verb, resource, categories, and query dimensions with no filler. Efficient, though the parenthetical category list makes it slightly dense.

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 one-parameter, read-only search tool with annotations and no output schema, the description covers what the tool is and how to query it, but leaves return-format and result-volume behavior unexplained. Adequate but with clear gaps.

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% and the single query parameter is already documented in the schema, including the note that omitting it lists all. The description restates the same query dimensions (país, materia, documento relacionado) without adding format or syntax detail, so baseline 3 applies.

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?

States a specific verb (Consulta) and a precise resource (convenios tributarios internacionales del SII), and enumerates the covered categories (doble imposición, intercambio de información, transporte internacional, convención multilateral). It is clearly distinguishable from sibling SII tools like sii_search_circulares. It does not explicitly name a sibling it is not, so 4 rather than 5.

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 how to use the tool (query by país, materia, or documento relacionado) but gives no when-to-use guidance, no exclusions, and no routing to alternatives like sii_buscar_resoluciones_y_oficios. Usage must be inferred.

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