engagement_details_delete

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Delete an engagement' implies a destructive, irreversible operation, but the description doesn't mention permissions required, whether deletion is permanent or recoverable, side effects on associated data, or any rate limits. This is inadequate for a destructive operation with zero annotation coverage.

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 maximally concise with just three words. While it's under-specified, it's not verbose or poorly structured. Every word serves a purpose, and there's no wasted language or unnecessary elaboration.

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 destructive deletion tool with no annotations, 0% schema description coverage, and no output schema, the description is completely inadequate. It doesn't explain what 'engagement' means, doesn't provide parameter guidance, doesn't warn about the destructive nature of the operation, and doesn't differentiate from sibling tools. This leaves the agent with insufficient information to use the tool 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 description coverage is 0%, meaning the single parameter 'engagementId' has no documentation in the schema. The description provides no information about this parameter - what format it should be in, where to find it, or what constitutes a valid engagement ID. With no parameter information in either schema or description, this fails to compensate for the coverage gap.

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 'Delete an engagement' is a tautology that merely restates the tool name 'engagement_details_delete'. It doesn't specify what type of engagement is being deleted or what 'engagement' means in this context. While the verb 'delete' is clear, the resource 'engagement' remains undefined, making this minimally informative.

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?

The description provides no guidance on when to use this tool versus alternatives. There are sibling tools like 'engagement_details_create', 'engagement_details_get', and 'engagement_details_update', but the description doesn't differentiate this deletion tool from them or explain when deletion is appropriate versus archiving or updating.

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