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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context about permissions, free business restrictions, and required pre-check steps, enriching the behavioral understanding 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?

The description is somewhat verbose, mixing purpose with procedural instructions. While it front-loads the core purpose, the additional directives on permissions and warnings could be more streamlined. It is adequate but not optimally concise.

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?

With no output schema, the description lists the metrics returned but not their format or structure. It covers prerequisites well, but the 5 parameters (0% schema coverage) lack sufficient explanation, and the return value details are missing. The description is incomplete for a full understanding.

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%, so the description must compensate. It mentions 'period' generically but fails to explain the meaning, format, or interaction of parameters like communityId, startDate, endDate, timezone, and period. This leaves significant ambiguity.

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 it retrieves completed sales, customers, gross sales, net revenue, and average order value for a managed business and period. However, it does not differentiate from similar sibling tools like get_business_summary or get_business_analytics, and the claim that 'business and community are interchangeable' may cause confusion.

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 guidance on prerequisites: check business permissions, call check_business_tool_access before collecting inputs, handle grace-period warnings, and never proceed when access is blocked. It also specifies that FREE businesses cannot use this tool.

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