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

Annotations already indicate destructive behavior. The description adds behavioral context beyond that: the confirmation requirement and permission checks. It doesn't contradict annotations and adds useful detail.

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 reasonably concise, with each sentence adding value. It is front-loaded with purpose and confirmation requirement. Slightly longer due to multiple conditions, but still efficient.

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 lack of output schema, the description covers essential aspects: confirmation, permission checks, and business restrictions. It adequately prepares the agent for usage. Missing details on return values or recovery are acceptable for this type of tool.

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 input schema has 0% coverage. The description only explains the confirm parameter ('set to DELETE'), but does not describe zeroLinkId or communityId. This leaves significant gaps in parameter understanding.

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 'Delete a Zero Link product,' which is a specific verb and resource. While it doesn't explicitly differentiate from other delete tools, the name and description together make the purpose clear.

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 guidelines: requires confirm set to DELETE, check business permissions, FREE businesses cannot use, call check_business_tool_access before collecting inputs, and show warnings. It clearly states when to use and when not, with alternatives implied by pre-checks.

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