Get analytics summary

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only says 'latest analytics row per accessible account,' leaving undefined what an 'analytics row' contains, how 'accessible account' is determined, what happens when no accounts are accessible, and whether results are sorted or paginated. The 'window' is also ambiguous relative to the windowDays parameter. This falls short for a tool with zero annotation support.

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 8-word sentence with no wasted words and front-loads the primary result. It is appropriately concise, though the brevity comes at the cost of essential detail, which is penalized in other dimensions.

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 tool has no output schema and no annotations, so the description is the sole source of context. It leaves key concepts undefined: 'analytics row,' 'window,' and 'accessible account.' An agent could invoke the tool but would not know what to expect in return or how to interpret results, making it incomplete even for a simple one-parameter tool.

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 schema has one optional integer parameter, windowDays, with 0% description coverage. The description only alludes to it with 'in the window,' omitting units, default behavior when omitted, and how it filters rows. Since the description is the only source of parameter meaning, this is a significant 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 states a clear resource ('analytics summary') with a specific scope ('per accessible account') and a temporal qualifier ('latest ... in the window'). It is understandable at a high level, but it does not explicitly differentiate itself from sibling analytics tools like get_account_analytics or get_bulk_post_analytics, so an agent must infer which one to choose.

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?

There is no guidance on when to use this tool versus alternatives. The phrase 'per accessible account' implies cross-account aggregation, but no sibling tools are named, and there is no mention of conditions, exclusions, or prerequisites. An agent gets no help distinguishing it from get_post_analytics, get_account_analytics, or refresh_analytics.

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