senado_search_processos

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

Description reveals return format `{ count, processos }` with field list, mandatory filter requirement, and date range limit (max 1 year). Annotations already declare readOnlyHint=true and openWorldHint=true; description adds behavioral constraints 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?

Single coherent paragraph front-loading purpose, then constraints, then output structure. Every sentence adds value; no redundancy.

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 exists (so return values documented), description covers search functionality, mandatory filters, date limit, and linkage to next step tool. Complete for a search tool with 8 parameters.

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% parameter coverage with descriptions. Description adds extra context: mandatory filter requirement and date window limitation, reinforcing and supplementing schema. Baseline 3, plus additional value.

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 processes via API endpoint v3 `/processo`, and distinguishes itself from sibling `senado_buscar_materias` as complementary. Specific verb+resource.

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 mandatory filter condition (at least one of sigla, numero, ano, autor, periodo) and maximum date window of 1 year. Mentions using returned id in sibling tool `senado_obter_processo`. Does not explicitly mention when not to use, but context clear.

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