senado_search_votacoes

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

Discloses returning votes in reverse chronological order, output structure fields, and that nominal votes are excluded. Complements readOnlyHint annotation.

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?

Concise, well-structured single paragraph that front-loads purpose, then temporal guidance, then other filters, then output format. Every sentence adds value.

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 temporal constraints, filtering combinations, output structure, and links to sibling tool for detailed votes. Adequate for all 10 parameters and output schema.

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?

Adds meaning beyond schema by explaining the mutual exclusivity of time filters and providing usage examples (e.g., full year). Schema coverage is 100% but description adds practical context.

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 searches and lists plenary votes with optional criteria, distinguishing it from sibling tools like senado_obter_votacao which gets details for a specific session.

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 explains when to use `dias` vs `dataInicio`/`dataFim`, and directs to `senado_obter_votacao` for nominal votes, providing clear alternatives.

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