sei_pesquisar_processos

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

Annotations indicate readOnlyHint=true; description aligns with a read-only search. It adds behavioral details beyond annotations: explains pagination (pagina=0 is first page) and parameter dependencies (e.g., custom date range requires data_inicio/data_fim).

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 concise and well-structured: overall purpose first, then bullet points for filters and pagination. Every sentence adds value without unnecessary repetition.

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 11 parameters and presence of output schema, the description covers the essential usage context (filters, pagination, date format, ID dependencies). It does not describe the output schema, but that's acceptable since the schema itself exists. It is sufficient 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 description coverage is 0%, so the description must explain parameters. It does so for most parameters: palavras_chave, busca_rapida, sta_tipo_data, id_unidade_geradora, id_assunto, grupo, pagina, data_inicio, data_fim, and date format. However, it omits 'limit' and doesn't detail 'descricao' beyond the first line.

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 searches processes by text, description, dates, unit, or subject, and distinguishes it from sibling tools like sei_listar_processos (listing vs searching) by specifying various filter parameters.

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?

Provides guidance on using keywords vs quick search, date format, pagination, and references to other tools for obtaining IDs (sei_listar_unidades, sei_pesquisar_assuntos, sei_listar_grupos_acompanhamento). It does not explicitly state when not to use the tool, but the context is clear.

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