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

Annotations already indicate mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). Description adds critical access control context: FREE businesses are restricted regardless of feature rows, and requires permission checks. Adds value beyond annotations.

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?

Four sentences with efficient structure: first sentence states purpose, remaining sentences provide usage guidelines. No redundant phrases, but could potentially be tightened by merging some guidelines.

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?

For a mutation tool with 3 parameters and no output schema, the description is incomplete. It lacks parameter explanations, so an agent cannot correctly construct the 'items' array. Usage guidelines are thorough, but parameter semantics are entirely missing.

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 description coverage is 0% and the description includes no explanation of the three parameters ('communityId', 'productId', 'items'). The agent receives no guidance on how to construct the input, especially the 'items' array with nested objects.

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 'Update inventory quantities' and the resource 'physical product managed by the authenticated Nas.com user'. It distinguishes from siblings like 'get_physical_product_inventory' 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?

Explicitly states prerequisites: check business permissions, FREE businesses cannot use, call 'check_business_tool_access' first, show grace-period warning and verified resubscribe link, never proceed when blocked. Provides clear when-to-use and when-not-to context.

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