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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's mention of permissions and access checks adds useful behavioral context beyond what annotations provide. No contradiction with 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 lengthy (4 sentences) but front-loads the purpose and then provides detailed usage instructions. It is structured but could be more concise without losing critical information.

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?

Despite detailed usage guidelines, the description lacks information about the return value (graph datapoints format) and parameter details. With no output schema, the agent is left without guidance on what the tool produces, making it 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 description coverage is 0%, and the description does not explain the parameters 'days' or 'communityId' beyond their names. The agent must infer meaning from parameter names alone, which is insufficient for a tool with no additional documentation.

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 graph datapoints for community analytics and explains that 'business' and 'community' are interchangeable. However, it does not strongly distinguish from its sibling tool 'get_business_analytics_graph', which serves a similar purpose for business contexts, potentially causing 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?

The description provides explicit instructions: check business permissions, note that FREE businesses cannot use, call 'check_business_tool_access' before collecting inputs, show grace-period warning and verified resubscribe link, and never proceed when access is blocked. This gives clear when-to-use and prerequisites.

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