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

Description says 'Delete' indicating a destructive operation, but annotations have destructiveHint=false, creating a contradiction. No additional behavioral details beyond the contradiction, so score is low.

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 and front-loaded with the core purpose, then lists prerequisites. It is slightly redundant (e.g., 'Requires confirm set to DELETE_EVENT' and later 'Show any grace-period warning...') but overall well-structured.

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?

The description covers preconditions and business restrictions well but lacks information about post-deletion behavior (e.g., idempotency, permanent deletion). The annotation contradiction reduces confidence. Without output schema, more completeness would be expected.

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%, so description must explain parameters. It only mentions the 'confirm' parameter and its required value, but does not describe communityId, challengeId, or checkpointId. It also implies confirm is required when schema marks it optional, causing confusion.

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 it deletes the event attached to a challenge checkpoint. It distinguishes from sibling tools like delete_event and delete_challenge by specifying the target and the required confirm parameter.

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 explicit preconditions: requires confirm set to 'DELETE_EVENT', check business permissions, FREE businesses cannot use, call check_business_tool_access before inputs, show grace-period warning and resubscribe link, and never proceed when blocked. This offers comprehensive guidance on when and how to use the tool.

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