get_overview_analytics

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

With no annotations provided, the description adequately discloses the tool's read-only nature by listing what it returns, but it could mention potential performance impacts or rate limiting. It is transparent about the data returned.

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 sentence with a clear structure, listing all return items concisely. It could be slightly shorter but is efficient and front-loaded with the 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?

Given the tool's complexity (many analytics fields) and no output schema, the description thoroughly enumerates all return types, including geo, device, UTM, and top links. The single parameter is fully covered by the schema and description.

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 the schema already describes the only parameter 'days' and its default. The description merely repeats 'Default lookback is 30 days,' adding no new semantic meaning beyond the schema.

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 starts with 'Get workspace-wide analytics across all links,' which uses a specific verb and resource, clearly distinguishing it from per-link tools like get_link_analytics. It lists many specific data types (clicks, time series, breakdowns) that fully define the tool's scope.

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 states the default lookback of 30 days and implies the days parameter for adjustments, but does not explicitly state when to use this tool versus alternatives like get_link_analytics or get_top_links. However, the phrase 'workspace-wide across all links' strongly implies its use case.

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