analytics_performance_summary

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

With no annotations provided, the description must carry full burden. It only states it gets metrics but does not disclose if it is read-only, requires authentication, has rate limits, or any side effects. The term 'aggregate' is vague.

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?

Single sentence with no wasted words. Front-loaded with verb and resource, then specifies metrics. Highly efficient.

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?

No output schema, but description partially compensates by listing metrics. However, it does not specify return structure (e.g., single object or array, per page or total). Adequate for a simple summary tool with 3 parameters.

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?

Description adds value beyond schema by listing the specific metrics returned (clicks, impressions, CTR, position) and linking 'last N days' to the days parameter. Schema coverage is 100%, so baseline 3, but the extra details raise it to 4.

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 retrieves aggregate performance metrics (clicks, impressions, CTR, position) for the last N days, specifying the verb 'Get' and the resource. It distinguishes itself from siblings by focusing on aggregated summary rather than detailed breakdowns, but does not explicitly differentiate.

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?

No guidance on when to use this tool versus alternatives like analytics_query or analytics_time_series. The description lacks context on prerequisites, use cases, or situations where other tools are preferred.

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