analytics_breakdown

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

Annotations already cover readOnlyHint=true, so the trailing "Read-only" adds nothing. The description does earn credit for two non-annotation facts: the Advanced Analytics plan gate and the "(everything else)" folding behavior that keeps totals reconciling. It still omits how long a large breakdown takes or any rate-limit/auth nuance.

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?

Three tight sentences, front-loaded with the core action and scope, with no filler. The stray "[#127113]" artifact is dead weight but minor.

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?

With no output schema, the description covers what an agent needs: scope (one dimension), the row-cap/folding semantics, the plan prerequisite, and read-only nature. It stops short of explaining reconciliation output fields or currency segmentation, though the schema's currency description partially covers the latter.

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 100%, so all 7 parameters (dates, limit, store, currency, dimension, workspace) are already documented in the schema with defaults and constraints. The description restates the dimension options already present in the enum and the limit-folding behavior already noted on the limit param, adding no new parameter meaning. Baseline 3 is correct.

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?

States a specific verb+resource ("Aggregate KPIs") and enumerates the exact dimensions it can break down by, which distinguishes it from a by-time tool. It never names the analytics siblings (summary/timeseries/portfolio), so an agent must infer the split from the phrase "broken down by one dimension" rather than being told.

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?

It supplies one hard prerequisite ("Requires an Advanced Analytics plan") which is genuinely useful for routing. However, it gives no explicit when-to-use guidance against analytics_summary, analytics_timeseries, or analytics_portfolio, leaving the agent to infer usage from the dimension phrasing alone.

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