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

Annotations already indicate destructiveHint=true, and the description adds important behavioral context: the need for a confirm parameter, business permission checks, and business type restrictions (FREE businesses cannot use). This adds value beyond the annotations, though it doesn't describe potential side effects or return values.

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 a single paragraph that efficiently conveys critical information without unnecessary fluff. While it could be broken into bullet points for readability, it is front-loaded with the main action and immediately useful instructions.

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 prerequisites, permission checks, and business type restrictions thoroughly. However, it omits details about what happens after deletion (e.g., confirmation message, irreversibility), which would enhance completeness for an agent.

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?

With 0% schema description coverage, the description only clarifies the confirm parameter ('Requires confirm set to DELETE'). It leaves folderId and communityId undocumented in terms of their role or constraints. This is a significant gap for a tool with three parameters.

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 action ('Delete a folder-backed product') and distinguishes it from sibling delete tools like delete_folder_item by specifying the resource type. However, it doesn't explicitly define what a folder-backed product is, so clarity is good but not maximal.

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 instructions on when and how to use the tool: requires confirm set to DELETE, mandates checking business permissions first, specifies that FREE businesses cannot use it, and outlines steps for handling blocked access. This is comprehensive guidance beyond basic usage.

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