senado_obter_materia

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

Annotations already indicate readOnly, idempotent, non-destructive. The description adds valuable behavioral context: truncation behavior with aviso for tramitacao/textos, ordering (most recent first), and that 'limite' applies only to those sections. 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 structured and front-loaded with the core purpose. It then details each secao value in bullet-like form. While somewhat lengthy, every sentence adds value and it is well-organized for an agent to parse.

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?

With an output schema existing, the description complements it by explaining the structure for each secao, ordering, truncation behavior, and dependencies (getting codigoMateria from sibling tool). It covers all aspects needed for an 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?

Schema coverage is 100%, but the description goes beyond by detailing the return structure for each secao value, explaining default limits (100 for tramitacao, 50 for textos), and that codigoMateria is obtained via sibling tool. This adds significant meaning beyond 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 the tool obtains data of a matter by codigoMateria, with optional secao parameter and default 'detalhe'. It explicitly references the sibling tool 'senado_buscar_materias' for obtaining the codigoMateria, distinguishing its purpose.

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?

The description provides clear guidance on when to use each secao value (detalhe for full details, tramitacao for history, textos for documents) and mentions default limits. It does not explicitly state when not to use, but it explains the context for each section and references the alternative tool for searching.

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