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

Annotations provide no safety hints, so description carries burden. It discloses reorder is a modification, requires permission checks, and has business-tier restrictions. Adds procedural steps, though it does not detail reversibility or success indicators.

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, front-loaded with purpose, followed by procedural steps. Could be more concise by merging repeated access-check instructions, but overall efficient for a permission-sensitive mutation tool.

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 purpose, permissions, and business restrictions adequately. Lacks details on return values, success/failure behavior, sync/async nature. Acceptable given no output schema, but room for improvement.

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 has 0% description coverage for parameters. The description mentions 'folder-backed products' but does not explain the parameters 'communityId' or the 'folders' array structure (communityFolderId, index). Minimal added value beyond schema.

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 first sentence clearly states 'Reorder folder-backed products for a managed community,' specifying the action (reorder) and resource (folder-backed products) with scope (managed community). Distinguishes from siblings like 'reorder_folder_items' and 'update_folder_product'.

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?

Explicitly states when not to use (FREE businesses), instructs to call check_business_tool_access before collecting inputs, and mandates showing grace-period warnings and resubscribe links. However, it does not mention alternatives or explicitly contrast with similar tools like 'reorder_folder_items'.

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