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

Annotations already indicate destructiveHint=true. The description adds significant context: the tool is destructive, requires a confirm parameter set to 'DELETE', denies usage for FREE businesses, and mandates prior access checks and warnings. This provides rich behavioral context beyond the annotations, with no contradiction.

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 (4 sentences) and front-loaded with the main action. It efficiently conveys key procedural steps without extra fluff. A slightly more structured format (e.g., bullet points) could improve scannability.

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 tool with 3 parameters and no output schema, the description covers permissions, preconditions, and the confirm requirement. However, it does not explain the sessionId or communityId parameters, leaving some ambiguity. Overall, it is fairly complete but has minor gaps.

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 description only partially addresses the confirm parameter (requires 'DELETE'), but does not explain sessionId or communityId. With 0% schema coverage, the description fails to compensate; more parameter details would be needed to aid the agent.

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 tool deletes a one-on-one session, with a specific verb ('Delete') and resource ('one-on-one session'). It distinguishes from sibling delete tools like delete_challenge or delete_event by specifying the session type and mentioning 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 guidance: it instructs to check business permissions before offering the action, call check_business_tool_access before collecting inputs, shows that FREE businesses cannot use it, and requires grace-period warnings and a resubscribe link, with a final instruction to never proceed when access is blocked. This clearly tells 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.