senado_contratos

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds value by specifying the limit behavior (default 50, max 500, truncation with `aviso`) and the structure of returned items (id, numero, objeto, empresa, etc.). No contradictions with 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?

Extremely concise: three sentences cover purpose, return structure, and usage guidance. No filler. Front-loaded with the most important information. Every sentence earns its place.

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 description covers purpose, filters, return structure (top-level and item fields), limit behavior, and how to use the result for further detail. Output schema exists, so full return value documentation is not required. The description is complete for a search tool of this complexity.

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%, so baseline is 3. The description adds context by listing the filterable fields and noting that filters are applied upstream. It also explains the `limite` parameter with default and max. This provides additional meaning beyond the individual parameter 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?

The description explicitly states 'Busca contratos administrativos do Senado por fornecedor, CNPJ, ano, número, objeto ou mão de obra', clearly identifying the tool's verb (search) and resource (administrative contracts). It distinguishes from sibling tools by directing the user to use the returned `id` with `senado_contratacao_detalhe` for more details.

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?

Provides explicit guidance on when to use the tool (to search contracts with various filters) and when to use alternative (for detailed contract info, use `senado_contratacao_detalhe`). Also explains the limit parameter behavior with default and maximum, and the truncation warning via `aviso`.

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