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

Annotations provide readOnlyHint=false, destructiveHint=false, openWorldHint=false. The description adds significant behavioral context: it requires confirm, has business permission checks, FREE business restriction, and access blocking conditions. No contradictions with 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 4 sentences, each adding necessary information. It is front-loaded with the core purpose and each subsequent sentence addresses a prerequisite or constraint. No wasted words.

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 it is a mutation with 5 required params and no output schema, the description adequately covers operational prerequisites and constraints. However, it does not describe the effects of the reset (e.g., what happens to existing points) or the return value, which would be helpful for an agent.

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 has 0% description coverage, so the description must compensate. It only adds value for the 'confirm' parameter (must be set to 'RESET_POINTS'), but does not describe the other 6 parameters (communityId, challengeId, participantId, checkpointId, notify, reason). Most are inferable from context, but the agent would benefit from more guidance.

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 action: 'Reset checkpoint points for a challenge participant.' The name and title are unambiguous and it is easily distinguished from sibling tools like 'award_challenge_checkpoint_points' which adds points.

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?

Explicit guidance is provided: requires confirm set to RESET_POINTS, check business permissions via check_business_tool_access, FREE businesses cannot use, show grace-period warning and verified resubscribe link, never proceed when access is blocked. This tells the agent exactly 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.