senado_notas_taquigraficas

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

The description adds significant behavioral context beyond the readOnlyHint and openWorldHint annotations. It details the output structure for each mode, the max 20 blocks per call in 'texto' mode, and the use of sequenciaInicio/sequenciaFim for pagination. No contradiction with 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 a single, well-structured paragraph that front-loads the purpose, then explains modes, usage context, and additional options. Every sentence is informative without redundancy, striking an excellent balance between detail and brevity.

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 the tool's complexity (6 parameters, two modes, filtering), the description covers the key points: return structure, mode differences, pagination, and source of 'id'. It is slightly lacking in error handling or edge cases, but overall it is thorough and provides sufficient context for an AI agent to use the tool correctly.

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?

With 100% schema coverage, baseline is 3. The description enhances parameter understanding by explaining the return structure per mode and the filtering behavior of 'orador'. It also clarifies the max 20 blocks for 'texto' mode, providing extra context not in the schema.

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 it retrieves official stenographic notes from plenary sessions or committee meetings. It distinguishes between two modes (resumo and texto) and explains how to obtain the session ID from sibling tools. This differentiates it from other tools in the list.

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 and how to get the required 'id' from sibling tools (senado_agenda_plenario, senado_resultado_plenario, senado_reuniao_comissao). It also suggests using senado_videos_taquigrafia for media, providing clear guidance on tool selection.

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