excluir_etapa_venda

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

The description states it deletes a stage, implying irreversibility, but lacks details on side effects, prerequisites (e.g., if the stage can be deleted when linked to sales), or required permissions. No annotations are present to compensate.

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 a single, concise sentence that conveys the core function. However, it is too brief for a deletion tool, lacking necessary details.

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 delete operation, the description fails to explain return values, error conditions, or any confirmation. The tool is underspecified given the lack of output schema and annotations.

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 single parameter id_etapa is not described in the schema or the description; schema coverage is 0%. The agent has no information on what value is expected or how to obtain it.

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 (excluir) and the resource (etapa de pedido/venda), distinguishing it from sibling delete tools like excluir_venda. However, it could be more explicit about the scope (e.g., within a pipeline).

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 such as excluir_venda or excluir_negocio. The description does not provide context for appropriate usage scenarios.

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