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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds critical behavioral context: the tool is permission-gated, requires prior access check, and FREE businesses are blocked. This adds significant 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?

Five sentences, each adding value: purpose, permission checks, access verification, user communication, and error handling. Front-loaded with purpose, no wasted words.

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?

Purpose and usage guidelines are thoroughly covered. Annotations handle safety. Missing parameter explanations slightly reduce completeness, but the tool is simple and the context is largely sufficient for correct invocation.

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 two parameters (productId, communityId). The description does not explain what these parameters represent or their expected format. For a tool with minimal schema coverage, the description should compensate but does not.

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 'Get inventory data for a managed physical product', specifying action (get) and resource (inventory data). This distinguishes it from siblings like 'update_physical_product_inventory' and other 'get_physical_product_*' tools.

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 instructions: check business permissions before use, FREE businesses cannot use it, call check_business_tool_access beforehand, show grace-period warning and resubscribe link, and never proceed when access is blocked. Clearly defines when and how to use the tool.

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