senado_contratacao_detalhe

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

Description discloses return format ({ id, tipo, secao, count, total, itens }), pagination (limite default 100, max 500), and behavior for empty sections (count 0, empty itens). It also notes 'campos conforme a API administrativa' aligning with openWorldHint annotation. No contradiction with readOnlyHint.

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?

Description is a single paragraph, each sentence contributes value. It is logically structured: purpose, parameter explanations, output format, usage prerequisites. Slightly verbose but efficient for the complexity. Could be shortened slightly.

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 tool's complexity (4 parameters, 2 required, enums, output schema present), the description covers prerequisites, valid combinations, error cases, pagination, and return structure. It is fully adequate for an agent to select and invoke correctly.

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 coverage is 100% but description adds significant meaning: explains each tipo (contrato firmado, ata de registro de preço, nota de empenho) and each secao (itens, pagamentos, garantias, aditivos, acionamentos) with constraints (aditivos only for contratos, acionamentos only for atas). This goes beyond enum descriptions.

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?

Description starts with 'Detalha uma seção específica de uma contratação', clearly stating the verb (detail) and resource (section of a procurement). It distinguishes from siblings by explaining that the id should be obtained from senado_contratos or senado_contratacoes_lista, positioning itself as a detail retrieval tool.

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 guidelines are implied: obtain id via sibling tools before using this. Description explains valid tipo/secao combinations and mentions error on invalid combos. It lacks explicit 'when not to use' but the context is clear.

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