Excluir personagem do Flow

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

Annotations already declare destructiveHint=true, and the description adds real value on top: the deletion is permanent and gated on explicit user confirmation of the name. It does not disclose side effects (e.g., what happens to videos or projects that reference the character), which is the remaining gap for an irreversible operation.

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 short sentences, zero redundancy, with the destructive nature front-loaded and the usage restriction immediately after.

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 full schema coverage, annotations carrying the safety profile, and no output schema to explain, the description covers what an agent needs to call it correctly. The one missing piece is the blast radius of the deletion, which matters for a permanently 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 description coverage is 100%, so the schema already explains nome, projeto and the confirmar const. The description's 'confirmar o nome' only loosely ties to the nome parameter and adds no format or disambiguation detail beyond the schema.

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?

States a specific verb and resource ('Exclui um personagem do Flow') and adds the irreversible qualifier 'PERMANENTEMENTE', which cleanly separates it from flow_personagem_editar, flow_personagem_criar and flow_personagens without needing to name them.

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?

Gives an explicit precondition for use: only when the user explicitly asks for deletion and confirms the name. It does not name an alternative tool (e.g., flow_personagem_editar for non-destructive changes), so it stops just short of the top score.

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