sei_alterar_anotacao_bloco_interno

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

Annotations already indicate non-read-only, idempotent, and non-destructive behavior. The description adds version requirements and an error recovery suggestion ('use sei_versao if unexpected error'). This provides some additional context beyond 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 short (two sentences) but lacks structure. The first sentence conveys purpose, but the second sentence is a version/error note that could be more concisely integrated. It is not front-loaded with the most critical 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?

Given that an output schema exists, return values are covered elsewhere. However, the description fails to provide guidance on parameter input or usage context. For a tool with three required undocumented parameters, this is insufficient for correct invocation.

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 input schema has 0% description coverage for its three required parameters (id_bloco, processo, descricao). The description does not explain what these parameters represent or their format, leaving the agent without sufficient information to use the tool correctly.

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 states 'Altera anotação de processo em um bloco interno', which clearly specifies the action (alter) and the resource (annotation of process in internal block). It distinguishes from sibling tools like sei_criar_anotacao (create) and sei_alterar_anotacao_bloco_assinatura (different block type).

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 includes version information and a troubleshooting tip but does not provide explicit guidance on when to use this tool versus alternatives like sei_criar_anotacao or sei_alterar_anotacao_bloco_assinatura. The agent must infer usage solely from the name.

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