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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds meaningful behavioral context: the need for a confirm value, permission checks, and warnings. However, it doesn't clarify if unpublishing is reversible or what the exact impact is beyond making the product unavailable.

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 relatively concise at four sentences, front-loading the core purpose. It could be more structured (e.g., bullet points for preconditions), but it is clear and efficient with no filler.

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 destructive nature and complex preconditions, the description covers the main points: purpose, required confirm value, business restrictions, permission checks, and warnings. It lacks details on error scenarios or output (but no output schema exists). Overall, it is sufficient for an agent to use correctly.

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 compensate. It explains that confirm must be set to 'UNPUBLISH', which adds crucial meaning. However, zeroLinkId and communityId are not described; their names are self-explanatory but no validation or usage hints are provided.

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 'unpublish' and the resource 'Zero Link product', making the tool's purpose immediately obvious. It distinguishes from sibling tools like publish_zero_link and delete_zero_link by specifying the action.

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 guidance: requires confirm='UNPUBLISH', check business permissions, FREE businesses cannot use, call check_business_tool_access first, show grace-period warning and resubscribe link, and never proceed when blocked. This is comprehensive and actionable.

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