sei_remover_sobrestamento

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

Annotations indicate that the tool is not read-only (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds the mutation action ('Remove'), which is consistent. However, it does not disclose additional behavioral traits like reversibility or permission requirements. The parameter format hint is useful but not behavioral.

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 extremely concise (two sentences) and front-loaded with the main action. Every word adds value, with no redundancy.

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 tool with one parameter and an output schema (present but not shown), the description covers the action and parameter format. It could be improved by clarifying prerequisites or side effects, but it is mostly complete for an agent.

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 description provides crucial format guidance for the 'processo' parameter ('protocolo formatado (ex: 50300.018905/2018-67) ou IdProcedimento'). Since the schema only specifies type 'string' with no format, the description compensates fully for the 0% schema coverage.

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 action ('Remove o sobrestamento') and the resource ('um processo no SEI'). The verb 'Remove' and noun 'sobrestamento' are specific, and it distinguishes from related tools like sei_sobrestar_processo (which adds suspension) and sei_listar_sobrestamentos (lists suspensions).

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 is provided on when to use this tool versus alternatives such as sei_sobrestar_processo or sei_listar_sobrestamentos. The description does not mention prerequisites or scenarios where this tool is appropriate.

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