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

Annotations already indicate readOnlyHint=true and destructiveHint=false. The description adds valuable context: it requires permission checks, interacts with another tool (check_business_tool_access), and involves access blocking with grace periods. This goes beyond the safety profile provided by 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 a single paragraph with clear front-loading of purpose, followed by sequential usage instructions. It is somewhat lengthy due to the inclusion of multiple conditional steps, but each sentence serves a purpose. Could be slightly more 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?

The description thoroughly covers access control and prerequisites, which is critical for this tool. However, it lacks details about the return data (no output schema), such as what metrics the overview contains or the expected date range format. This leaves the agent without a clear picture of the output.

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?

The input schema defines two parameters (communityId, startDate) with 0% schema description coverage. The description does not explain what values these parameters accept (e.g., date format, ID scope), leaving the agent with no semantic guidance beyond the schema itself.

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 gets a monthly analytics overview for a community, noting that business and community are interchangeable. However, there is a sibling tool 'get_community_monthly_analytics_overview' with almost identical naming, and the description does not differentiate between them, leaving ambiguity.

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 explicitly states prerequisites: check business permissions, call check_business_tool_access before collecting inputs, show grace-period warning and resubscribe link, and never proceed when blocked. It also specifies that FREE businesses cannot use this tool. This provides 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.