sei_excluir_bloco_interno

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

Annotations already mark as destructive (destructiveHint=true). Description adds that it deletes blocks and mentions version requirements, but does not detail side effects (e.g., impact on enclosed processes). Adequate but not rich.

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 concise sentences plus version line, front-loaded with the main action. No redundant or irrelevant 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?

With output schema present, return values are not needed. One parameter explained. However, lacks information on error conditions or idempotency. Mostly complete for a simple destructive tool.

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%; description adds 'IDs separados por vírgula' clarifying the input format for ids_blocos. This adds meaning beyond the schema's bare title but could be more explicit (e.g., 'IDs dos blocos internos').

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 'Exclui bloco(s) interno(s)' (deletes internal block(s)), specifying the action and resource. Differentiates from sibling tools like sei_excluir_bloco_assinatura and block manipulation tools.

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?

Provides version availability and a troubleshooting hint, but no explicit guidance on when to use this tool vs alternatives (e.g., when to delete vs conclude or reabrir a block). Does not mention prerequisites or context.

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