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

Annotations indicate destructiveHint=true, but the description adds behavioral context beyond that: the confirm parameter requirement, permission checks, free business restriction, and the need to show warnings. It does not contradict annotations and provides necessary safety context.

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 concise (two sentences) yet packs critical instructions. The core action is front-loaded, and every sentence adds value—no wasted words. It balances completeness with brevity.

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?

Despite having no output schema, the description covers prerequisites, permissions, business restrictions, and error-handling steps. It provides sufficient context for an AI agent to safely invoke this destructive tool, addressing all major concerns for a deletion operation.

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 has 0% description coverage for three parameters. The description clarifies the confirm parameter must be set to 'DELETE' but does not explain productId or communityId. Since schema descriptions are missing, the description partially compensates by documenting one parameter's expected value.

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 starts with 'Delete a physical product,' clearly stating the verb and resource. Among many sibling delete tools (e.g., delete_challenge, delete_event), this description uniquely identifies the target physical product, distinguishing it from similar operations.

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 explicit when-to-use guidance: requires confirm parameter set to 'DELETE', mandates checking business permissions via check_business_tool_access, prohibits free businesses from using the tool, and instructs on handling grace-period warnings and resubscribe links. It also states conditions to never proceed, offering clear usage boundaries.

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