buscar_processo

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

Annotations are entirely absent, so the description carries the full burden. It discloses the search criteria but doesn't mention that the operation is read-only, any rate limits, pagination behavior, or what the response contains. This is a notable gap for a search tool.

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, front-loaded sentence that directly conveys the purpose and parameter semantics with zero wasted words.

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?

For a simple one-parameter search tool with an output schema, the description covers the core purpose and parameter meaning. Still, it lacks explicit usage guidelines and behavioral details (e.g., read-only confirmation), leaving some gaps for an AI agent deciding between tools.

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?

The single parameter 'termo' is explicitly explained as accepting a CNJ number, party name, or CPF/CNPJ, which adds significant meaning beyond the bare schema. However, it doesn't specify formatting details (e.g., CNJ punctuation), so it's not exhaustive.

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 processos in SPA-PMT by CNJ number, party name, or CPF/CNPJ, with a specific verb ('Busca') and resource. It distinguishes itself by noting it's the global top-of-system search, but it doesn't explicitly name alternative tools for different use cases.

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 phrase 'a busca global do topo do sistema' implies this is the general-purpose search tool, but it doesn't explicitly state when to use it over siblings like obter_processo or listar_caixa, nor does it mention any exclusions or prerequisites.

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