deleteEntitlement

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

Despite no annotations, the description warns 'DESTRUCTIVE: cannot be undone' and explains the approval process. It adds context about irreversible effects but could mention potential side effects or required permissions.

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 concise with three sentences, each serving a purpose: stating the action, emphasizing destructiveness, and providing usage instructions. No fluff.

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 deletion tool with one required parameter, the description covers purpose, destructiveness, and confirmation flow. It lacks return value information but is otherwise sufficient.

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 100% with clear descriptions for entitlementId and __userContext. The description does not add parameter meaning beyond the schema, so baseline score of 3 is appropriate.

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 explicitly states 'Permanently delete an entitlement.' It clearly identifies the verb (delete) and the resource (entitlement), distinguishing it from sibling tools like createEntitlement or updateEntitlement.

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 specific guidance: 'ONLY call when the user explicitly says delete or remove for THIS entitlement.' It also clarifies that the host enforces confirmation via an approval gate and instructs the agent not to ask for re-confirmation, reducing ambiguity.

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