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

Annotations provide little insight (destructiveHint false, readOnlyHint false). The description does not explain the consequences of cancellation, whether it is reversible, or any behavioral traits beyond the minimal action. The user remains uninformed about side effects.

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 very concise with two sentences and no wasted words. However, it could be slightly more informative without becoming verbose, so it is good but not perfect.

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?

Given the tool has three parameters (including a required one) and no output schema, the description is insufficient. It does not explain the return value, the effect of cancellationReasons, or how the tool fits into the broader workflow of plan management.

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 the description must compensate. It adds value for the 'confirm' parameter by specifying the required value 'CANCEL_PLAN', but does not explain the 'communityObjectId' or 'cancellationReasons' parameters, leaving gaps.

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 verb 'Cancel' and the resource 'community plan', which is specific. However, it does not differentiate from sibling tools like 'delete_plan' or 'revoke_plan_cancellation', leaving ambiguity about when to use this tool over others.

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 only mentions a prerequisite ('Requires confirm set to CANCEL_PLAN') but provides no guidance on when to use this tool versus alternatives, such as when to cancel vs delete a plan or when to revoke a cancellation.

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