sei_remover_atribuicao

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

Annotations already declare readOnlyHint=false and destructiveHint=false. Description adds that it removes from 'any user', which is useful context. However, it doesn't elaborate on permissions, side effects, or reversibility. With annotations covering the safety profile, a 3 is appropriate.

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?

Two-line description with a bullet for the parameter. Front-loaded with purpose. Every sentence earns its place. No 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?

Given the simple one-parameter tool and presence of an output schema, the description covers the action and parameter format adequately. However, adding a comparative hint to sei_atribuir_processo would improve completeness.

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 description must compensate. It states 'processo: protocolo formatado ou IdProcedimento', which adds format semantics (protocol vs internal ID) beyond the schema's bare string type. This is valuable but could be more explicit.

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?

Description clearly states 'Remove a atribuição de um processo (desatribui de qualquer usuário)' – a specific verb and resource. It distinguishes from sibling tools like sei_atribuir_processo (assign) and sei_consultar_atribuicao (consult).

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?

No guidance on when to use this tool versus alternatives like sei_atribuir_processo or sei_cancelar_assinatura. No when-to-use or when-not-to-use information provided.

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