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

Annotations already declare readOnlyHint=true, and the description confirms a read operation. It adds valuable behavioral context: FREE businesses cannot use it, permission checks are required, and there is a prerequisite tool call. This goes beyond the 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?

The description is moderately concise but includes a clarification about business/community interchangeability that may not be needed. It front-loads the purpose and then adds procedural steps. Could be slightly shorter without losing clarity.

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 complexity (8 parameters, no output schema, no nested objects), the description covers purpose, prerequisites, and restrictions. It mentions the output fields but lacks details on response structure, pagination, or sorting behavior. Parameter semantics are not addressed, leaving gaps.

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 coverage is 0%, meaning no parameter descriptions in the schema. The description only indirectly references 'period' and does not explain the meaning, format, or constraints of the 8 parameters (e.g., timezone, sortBy, limit). It does not compensate for the lack of schema descriptions.

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 ranked product sales, customers, gross sales, net revenue, and average order value for a single business and period. The title and name align well. It distinguishes from many sibling tools by specifying a focused sales data function.

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 prerequisites: check business permissions, call check_business_tool_access, and handle grace-period warnings. However, it does not compare to similar tools like get_business_sales_summary or get_business_analytics, so the when-to-use vs alternatives is implied rather than explicit.

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