senado_agenda_plenario

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is clear. The description adds value by detailing the return structure (data, escopo, count, sessoes) and session fields (codigo, data, hora, tipo, situacao, pauta), which goes beyond 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?

The description is one dense paragraph that front-loads the purpose, then returns structure, then usage, then related tools. Every sentence earns its place with no wasted words.

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?

For a tool with 3 parameters, no required fields, and an output schema, the description fully explains the return structure, parameter behavior, and related tools. It is complete for effective use without needing additional context.

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%, providing baseline of 3. The description adds meaning by explaining the escopo enum values (dia, mes, cn), default for data (today), and that dataFim is only for escopo=cn. This contextualizes the schema beyond its minimal 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 clearly states the tool obtains the agenda of plenary sessions for Senate or National Congress, with specific fields returned. It distinguishes itself from siblings like senado_encontro_plenario and senado_resultado_plenario by mentioning when to use those instead.

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 this tool versus alternatives (e.g., 'Para o resultado já apreciado use senado_resultado_plenario; detalhes de uma sessão via senado_encontro_plenario'). Also explains parameter defaults and scope behavior ('Use escopo dia/mes/cn; sem data assume hoje').

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