sei_reabrir_bloco_interno

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

Annotations already indicate mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds no further behavioral context, such as prerequisites, side effects, or what reopening entails. Minimal value beyond the name.

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?

Description is short (three lines) and front-loaded with the action. However, the version note and error tip add minor value and could be removed or relegated to a notes section.

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?

Despite having an output schema (not shown) and simple parameter, the description lacks essential context: what is a 'bloco interno', what state must it be in, what reopening achieves, and what the output contains. An agent would need external knowledge to use this correctly.

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%, yet the description provides zero information about the required parameter 'id_bloco'. No guidance on format, source, or semantics, leaving the agent completely uninformed.

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 the tool's action clearly: 'Reabre bloco interno concluído' (reopens concluded internal block). The verb 'reabre' and resource 'bloco interno concluído' are specific, and it distinguishes from sibling tools like 'sei_concluir_bloco_interno' (concludes) and 'sei_reabrir_bloco_assinatura' (reopens signature block).

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_concluir_bloco_interno' or 'sei_reabrir_bloco_assinatura'. The version info and error tip are technical but do not help an agent decide context of use.

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