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

Annotations indicate readOnlyHint=true and destructiveHint=false, so the description's behavioral context is not critical, but it adds value by explaining the access restrictions and prerequisite checks. No contradictions. The description could mention rate limits or data volume if applicable, but overall it supplements annotations well.

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 5 sentences and effectively front-loads the purpose. It could be slightly tighter by removing the redundant 'Business and community refer to the same thing and are interchangeable.' However, it is still concise and clear.

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 moderate complexity (7 params, no output schema, read-only annotations), the description covers prerequisite checks well but omits parameter semantics and return value expectations. The presence of multiple sibling analytics tools suggests more differentiation could be helpful, but the usage guidelines are thorough.

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 description coverage and 7 parameters, the description should explain more. It only hints that 'filter' distinguishes between Source and Products analytics, and 'communityId' refers to the community. Other parameters (startDate, endDate, duration, productId, isCommunityPage) are not explained, leaving the agent unclear on their usage.

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 analyticsV2 source or product analytics for a community, distinguishing it from sibling tools like get_business_analytics (likely v1) and get_community_analytics by specifying 'analyticsV2' and the filter options. The verb 'get' plus resource 'analyticsV2 source or product analytics' is specific.

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