senado_ceaps

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

Annotations provide readOnlyHint and openWorldHint. Description adds detailed behavioral context: output structure for each mode, pagination with limite cap 100 and aviso on truncation, and partial search behavior. No contradictions.

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 moderately long but well-structured. Front-loaded purpose, then output, then filters, then pagination. Each sentence adds value. Could be slightly tighter but overall efficient.

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 8 parameters, multiple modes, and output structure, the description covers all essentials: modes, filters, pagination, and cross-reference to another tool. No gaps for correct invocation.

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 meaning: explains that filters like nomeSenador, tipoDespesa, fornecedor use partial search, and describes the mode parameter with default value. This goes beyond schema 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 clearly states it retrieves CEAPS expenses for senators in a given year. It specifies verb 'Retorna' and resource 'Despesas... CEAPS'. While it mentions sister tool for codSenador, it doesn't explicitly differentiate from all siblings, but overall purpose is unambiguous.

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?

Description explains when to use each mode ('agregados' vs 'detalhe') and how to filter by various fields. It advises using senado_listar_senadores to obtain codSenador. No explicit exclusions, but context is clear.

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