ghl_social_get_statistics

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

Discloses OAuth scopes (socialplanner/statistics.readonly) indicating read-only behavior. No mention of side effects; annotations consistent except for readOnlyHint false. Does not explain why endpoint is POST.

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?

Concise main description with defaults; endpoint and scopes appended. Slightly verbose but well-structured with front-loaded purpose.

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?

Covers input behavior and defaults well, but missing output description (no output schema exists). Needs to describe what kind of analytics data is returned.

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 100% and description does not add meaning beyond what the schema already provides for parameters.

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?

Clearly states verb 'retrieve' and resource 'analytics data for multiple social media accounts.' Distinguishes from siblings which are ad-related or social post management tools.

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?

Implies usage for retrieving social media statistics with date defaults, but no explicit guidance on when to use vs alternatives like ghl_social_get_posts.

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