senado_execucao_orcamentaria

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

Describes return structure (tipo, modo, ano, totalLinhas, agregado[] or despesas[]/receitas[]), truncation with aviso, and ordering. Annotations confirm read-only, safe behavior.

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?

Single dense paragraph with clear flow: purpose, return format, usage, differentiation. Efficient but could be more structured with bullets for readability.

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?

Covers all key aspects: data scope, parameter interplay, result format, filtering advice, and sibling differentiation. Output schema likely fills remaining 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 covers 100% of parameters, but description adds context: links modo to tipo, explains ano for volume reduction, and notes default limite.

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?

Clearly states it covers Senate budget execution (expenses and revenues), lists year ranges, and distinguishes from sibling tool senado_orcamento_parlamentar.

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?

Explicitly instructs when to use each tipo with corresponding modos, recommends filtering by ano before detalhe, and warns against confusion with another tool.

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