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

Discloses financial-data permissions, business restrictions, and UI requirements (grace-period warning, resubscribe link) beyond the readOnlyHint annotation, adding valuable behavioral context.

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 concise: five sentences, front-loaded with purpose, and includes essential usage instructions without unnecessary details.

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?

Despite clear usage guidelines, the description omits what the analytics contain or the return format; with no output schema, the agent lacks sufficient context to interpret results.

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 coverage and no parameter descriptions in the description, it fails to add any meaning about the 5 parameters (communityId, productId, dates, etc.), leaving the agent uninformed about input requirements.

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 tool retrieves analytics for a managed physical product, using a specific verb and resource, which distinguishes it from siblings like get_physical_product_inventory.

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 instructs to check business permissions, call check_business_tool_access before collecting inputs, and explains that FREE businesses cannot use this tool, providing clear when-to-use and when-not-to-use guidance.

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