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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety burden is lower. The description adds useful behavioral context beyond annotations, including the ~100-user sample-size caveat and the last-28-days window for `stores`.

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 front-loaded and compact, with each sentence adding useful information: view definitions, sample-size caveat, and store-specific scoping. There is little or no filler.

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?

For a one-parameter read-only tool with no output schema, the description is largely complete because it summarizes the return content for every view. It does not specify default date ranges for `overview`, `funnel`, or `cohorts`, nor does it describe response shape or pagination.

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 the baseline would be 3, but the description earns above that by explaining what each of the four `view` enum values actually returns. It turns the enum into actionable semantics rather than just repeating `Which analytics view to return`.

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 specific analytics resource and clearly enumerates the four views, so the agent knows what the tool does. It does not explicitly distinguish this tool from sibling analytics tools, especially get_store_analytics, which overlaps with the `stores` view.

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 explains what each view returns, so choosing among the four enum values is implied. However, it never states when to use this tool instead of sibling tools such as get_store_analytics or get_acquisition_report, and gives no explicit when-not guidance.

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