sei_arvore_processo

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

The description goes beyond the annotations (readOnlyHint=true, openWorldHint=true) by detailing the default backend (REST endpoint) and the optional web scraper mode with its activation condition and status. This provides useful implementation context without contradicting the read-only nature indicated by 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 well-structured with the main purpose first, followed by parameter clarification, cross-reference, and implementation detail. It is concise but not overly terse; each sentence adds value. Minor improvement could be restructuring to reduce repetition about the scraper.

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 simplicity (1 parameter, output schema exists), the description covers all necessary aspects: what it does, how to specify input, alternative tools, and backend behavior. No critical omissions are apparent.

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?

With 0% schema description coverage, the description fully compensates by explaining the single parameter: it accepts a formatted protocol (with example) or IdProcedimento. This adds critical meaning beyond the schema's bare type declaration.

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 explicitly states 'Mostra a árvore (lista) de documentos de um processo SEI', which is a specific verb (mostra) and resource (árvore de documentos). It distinguishes itself from sibling tools like sei_ler_documento by offering a tree view rather than content reading, and from other listing tools via the focus on document hierarchy.

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 clearly indicates when to use this tool (to view the document tree) and provides an explicit alternative for reading document content ('use sei_ler_documento com o id'). It also mentions the default REST method and the scraper option with an env variable, offering context on performance. However, it does not explicitly compare to other nearby sibling tools like sei_listar_documentos or sei_consultar_processo.

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