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

Annotations already cover the read-only safety profile, and the description adds real context beyond them: the plan requirement (Advanced Analytics/Pro/Enterprise), the default 30-day window, and prior-period deltas. It does not state rate limits or the shape of the delta output, but the auth/access disclosure is genuinely valuable.

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?

Front-loaded with the resource and metric list, followed by defaults and plan requirement in efficient sentences. However, the trailing '[#6b72a2]' artifact is stray noise that slightly detracts from an otherwise tight, low-waste definition.

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 exists, but the description enumerates the returned KPIs, effectively documenting the response. Combined with the plan prerequisite and default window, an agent has what it needs to invoke correctly, with only minor gaps (no mention of breakdown/timeseries routing).

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%, so all five params (start, end, store, currency, workspace) are already fully documented in the schema. The description only restates the date-range default, adding no new syntax or semantics. Baseline 3 applies when the schema does the heavy lifting.

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 (headline order/merch KPIs for a date range) and enumerates the concrete metrics returned, so an agent knows exactly what it produces. It implicitly distinguishes itself from analytics_breakdown and analytics_timeseries via 'headline'/'summary', but never names those siblings, so the differentiation is left to inference.

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?

Provides useful scoping context ('defaults to the last 30 days') and a plan prerequisite, but gives no explicit when-to-use guidance versus the analytics_breakdown, analytics_timeseries, or analytics_portfolio siblings. Usage is only implied by the word 'headline'.

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