senado_resultado_plenario

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

Discloses return structure, pagination (none), null fields for undecided items, and edge case of no session (count=0, sessoes empty). Annotations already indicate read-only and idempotent, so description adds specific behavioral context.

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 well-structured with front-loaded purpose, then return details, edge case, and sibling references. Slightly long but 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?

Given output schema and annotations exist, the description covers return format, parameter details, edge cases, and distinguishes from siblings. No 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 has 100% description coverage, but description adds meaning: date pattern YYYYMMDD and that escopo=mes accepts any day of the month. It also explains the three escopo values in Portuguese.

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 returns results of plenary sessions on a date, listing items, opinions, and outcomes. It distinguishes from sibling tools like senado_agenda_plenario and senado_orientacao_bancada.

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 tells when to use (results of plenary sessions) and when not to (use senado_agenda_plenario for agenda, senado_orientacao_bancada for bancada orientation). Also explains escopo parameter.

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