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

Annotations already mark it read-only, non-destructive and closed-world; the description adds useful context: it opens a dashboard beside the chat, the merchant can switch period and open a catalog in the panel, and a plan with analytics is required. It does not describe error behavior or data freshness, but with annotations and an output schema it provides substantial behavioral context.

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 verb and resource, then the content, prerequisite and alternative. It is dense and somewhat long, but each clause (catalog mode, panel interaction, plan requirement, alternative tool) carries useful selection information.

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?

Complete enough for a read-only dashboard tool: content, scope, prerequisite and alternative are present, and the output schema covers return values. No essential calling detail is missing.

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 is 3. The description adds meaningful semantics for catalogId: it changes the output to that catalog's top products, most viewed pages, live visitors and collected leads, not merely a filter. It also reinforces the period parameter by noting that the merchant can switch periods in the panel.

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?

Opens a specific resource ('analytics as a dashboard') and enumerates the views, visitors, clicks, top catalogs, referrers, countries and devices, so the agent knows exactly what appears. It explicitly separates overview mode from catalog-scoped mode and names get_analytics as the adjacent tool.

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?

States the situation ('when they want to see how things are going') and the alternative for a specific numeric question ('get_analytics'). It also adds the prerequisite ('Needs a plan with analytics'), leaving little ambiguity about when to use it.

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