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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows it's a safe read operation. The description adds value by disclosing critical business rules: free businesses are blocked irrespective of feature rows, and a grace-period warning/resubscribe link must be shown. This goes beyond what annotations provide.

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 five sentences, front-loading the purpose, then providing essential usage instructions. Every sentence adds value (purpose, clarity on business/community, permission check, access rule, warning). It is concise without being overly verbose.

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 covers critical behavioral context (access control, prerequisites) but lacks parameter explanations. Since there is no output schema, the description does not describe return values. For a read tool with moderate complexity, this is adequate but incomplete.

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%, so the description must compensate by explaining parameters, but it does not. It mentions no details about what 'days' or 'communityId' mean, leaving the agent to infer from names only. This is a major gap.

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 gets graph datapoints for community analytics and clarifies that 'business' and 'community' are interchangeable. However, there is a sibling tool 'get_community_analytics_graph' with a similar name, which could cause confusion; the description does not differentiate from it.

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, free businesses cannot use, call check_business_tool_access before collecting inputs, show grace-period warning, and never proceed when blocked. It effectively tells when to use (after access check) and when not to (blocked access).

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