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

Discloses behavioral traits: deletion requires confirmation, restricted for free businesses, and prerequisites before offering. However, it does not mention reversibility or side effects. With annotations providing only readOnlyHint=false and destructiveHint=false, the description adds useful context but could be more explicit about destructive nature.

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?

Five sentences with key info front-loaded. Could be slightly more concise, but each sentence adds value and no redundancy.

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 essential steps for using the tool: prerequisites, permission checks, and warnings. No output schema, but return value expectation is implied. Adequate for an agent to proceed safely.

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?

Adds meaning to the 'confirm' parameter by stating it must be 'DELETE', which is not in the schema. No additional info for upsellId or communityId, but schema coverage is 0%, so description partially compensates.

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 an upsell, which is a specific verb and resource. It distinguishes from siblings like create_upsell and update_upsell.

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?

Provides explicit usage instructions: requires confirm set to 'DELETE', check business permissions, free businesses cannot use, call check_business_tool_access, show grace-period warnings and resubscribe link. No alternatives mentioned, but the context is comprehensive.

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