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

The description adds minimal behavioral context beyond the annotations which already indicate readOnlyHint=true and destructiveHint=false. It does not describe what the 'impact' includes (e.g., fees, feature restrictions) or any edge cases. The description does not contradict annotations.

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 a single, front-loaded sentence that is concise. However, it sacrifices necessary detail for brevity. It earns most points for efficiency but loses one due to missing parameter information.

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's complexity (plan management in a community context), the description is inadequate. It does not explain what 'impact' means, what data the preview returns, or any conditions that might affect the preview. The presence of annotations only partially compensates.

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 schema description coverage is 0%, and the description does not mention the parameter 'communityObjectId' at all. It fails to explain what this parameter represents or any constraints beyond the schema definition. The parameter name is somewhat self-explanatory, but the description should provide context.

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 'Preview' and the resource 'plan cancellation impact for a community'. It distinguishes itself from sibling tools like 'cancel_plan' and 'revoke_plan_cancellation' by explicitly indicating it is a preview of impact, not the action itself.

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. It does not mention prerequisites, typical use cases, or when not to use it. For example, it does not indicate that this should be called before 'cancel_plan' to assess impact.

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