delete_engagement

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

No annotations are provided, so the description carries the full behavioral burden, and it adds nothing beyond the word 'delete'. It does not disclose irreversibility, whether attached tests/findings are cascaded or orphaned, or required permissions — significant gaps for a destructive 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?

The text is short and the purpose sentence is front-loaded, which is good. The 'Args:' block is redundant boilerplate that restates the single obvious parameter rather than earning its space.

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?

An output schema exists so return values need not be explained, but for a destructive tool with zero annotations the description should at minimum cover cascade behavior, irreversibility, or preconditions. None of that is present.

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 0%, but there is only one parameter and its name is self-explanatory; the description restates it as 'the engagement ID to delete' without adding format or sourcing details. This is adequate but adds no meaning beyond the schema title.

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 a specific verb (delete) and resource (engagement), which is unambiguous on its own. It does not, however, differentiate itself from the many other delete_* siblings (delete_organization, delete_product, delete_finding, delete_test), so an agent gets no help choosing among them from the text alone.

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?

There is no when-to-use, when-not-to-use, or prerequisite guidance. Nothing states whether the engagement must be closed or empty first, or that findings/tests inside it may be affected, which matters given the sibling close_engagement and reopen-style tools.

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