sei_resumo_processos

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that the tool fetches all processes from the current unit and groups them, which is consistent and provides extra context. No contradictions.

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: a concise purpose sentence, then an explanation, a clear bullet list of available fields, and illustrative examples. No redundant information.

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?

The tool is adequately explained for its purpose with good examples, but missing documentation for two parameters (filtro, apenas_meus) prevents full completeness, especially given output schema exists but is not shown.

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 0%, so the description must compensate. It thoroughly documents agrupar_por and agrupar_por_2 with a list of allowed values and examples, but fails to explain filtro and apenas_meus, leaving a gap.

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 generates a grouped summary of processes from the current unit's inbox, using specific verb 'Gera um resumo agrupado'. It distinguishes from sibling tools like sei_listar_processos or sei_pesquisar_processos by focusing on aggregation.

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?

Examples show different grouping scenarios, providing clear context for when to use the tool. However, it lacks explicit guidance on when not to use it or direct comparison with alternatives.

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