senado_buscar_materias

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

Annotations provide readOnlyHint and openWorldHint; description adds details about return structure, truncation warning, and the need to provide at least one criterion. No contradictions. Additional behavioral traits like pagination and limit behavior are disclosed.

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 with three main sentences covering purpose, return structure, and cross-reference. No superfluous words, though could be slightly more streamlined.

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 (7 parameters, search functionality), the description covers all essential aspects: search criteria, default/limit, return format, truncation, and linkage to a sibling tool. Output schema is referenced, making it complete.

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% with adequate descriptions; the description adds value by specifying 'at least one criterion' and mapping fields from the response (codigo, sigla, etc.), enhancing understanding beyond 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 searches legislative matters with specific criteria (type, number, year, keywords, author, situation) and distinguishes from sibling tool 'senado_obter_materia' for retrieving details. The verb 'Busca' and resource 'matérias legislativas' are precise.

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 states 'informe ao menos um critério' and lists searchable parameters. Cross-references 'senado_obter_materia' for detail retrieval, providing context. Lacks explicit when-not-to-use or alternatives, but the guidance is clear.

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