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

Annotations declare destructiveHint=true, and the description adds required confirm=DELETE, permission checks, and free business restriction. No contradiction; adds valuable behavioral context beyond 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?

Every sentence serves a purpose: purpose first, then prerequisites and warnings. No redundancy, front-loaded with core action. Efficient and clear.

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?

Covers permissions, precondition checks, and required input value. Lacks return behavior details, but with no output schema and clear action, this is sufficient. Could mention success/failure indications but not necessary.

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 coverage is 0%, so description must add parameter meaning. It specifies confirm must be 'DELETE', but does not explain communityId or messageId. The tool name hints at messageId, but communityId remains vague. Partial compensation.

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 'Remove the schedule from a Magic Reach message,' providing a specific verb and resource. It distinguishes from the sibling tool 'delete_magic_reach_message' which deletes the message itself, not just its schedule.

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?

Explicitly gives step-by-step prerequisites: check business permissions, use check_business_tool_access before collecting inputs, show grace-period warning and resubscribe link, and never proceed when access is blocked. Also notes FREE businesses cannot use this tool.

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