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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the bar is lower. The description nonetheless adds real behavioral context beyond them: the attribution-footer handling contract and the explicit 'data accuracy contract' telling the agent not to invent or infer missing metrics. It does not, however, describe auth requirements, rate limits, or data freshness.

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 opening sentence is well front-loaded and specifies purpose and output. However, the bulk of the text is verbose contract language (attribution footer rules, long list of things not to invent) that repeats itself and dilutes the core message. Every sentence earns some place, but the density could be tighter.

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?

An output schema exists, so return-value explanation is unnecessary, and annotations cover safety. For a 2-parameter dashboard tool this is nearly complete, with the accuracy contract and attribution handling filling behavioral gaps. The missing piece is explicit routing guidance against sibling connectors/dashboards.

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 both parameters (start_date, end_date) are already fully documented in the schema with formats, defaults, and patterns. The description's 'date-bounded' wording reinforces but adds no syntax or edge-case detail beyond what the schema provides. Baseline 3 applies.

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 and resource ('Fetch complete date-bounded Shopify orders and shop metadata') plus the concrete output (verified PNG dashboard covering order value, order count, AOV, trend, status breakdown). The purpose is clear and distinct from generic connectors. It stops short of naming a sibling (e.g., shopify_connector) to route against, which would earn a 5.

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 never states when to use this tool versus alternatives such as shopify_connector or other *_dashboard tools. The only conditional guidance ('When tool output supplies an attribution footer...') governs response formatting, not tool selection. No when-to-use or exclusion guidance is present.

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