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

Annotations already declare readOnlyHint, idempotentHint and destrictiveHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond that: results depend on the store's plan, implying empty or partial results are possible without error. It does not say what is returned or whether any auth/scope is required beyond that.

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?

It is short with no filler, but it is a sentence fragment rather than a front-loaded statement of what the tool does, so the brevity comes at the cost of basic specification. Nothing is wasted, yet the single clause does not earn its place as a complete 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?

With no output schema, the description carries the burden of describing returns, and it does not — an agent cannot tell whether it receives a list of report definitions, report data, or metadata, nor how to request one specific report despite the singular 'get_report' name. For an open-world external-service read tool, that gap matters.

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?

There is a single optional parameter and the schema describes it fully (workspace id from list_projects, omit for default), so schema coverage is 100% and baseline 3 applies. The description adds nothing about project_id, but nothing is missing from the schema either.

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 identifies the resource (Shopify saved reports) but is a bare noun phrase with no verb — it never says whether the tool lists, retrieves, or generates reports. It also gives no differentiation from the many sibling shopify_list_* tools, so an agent cannot tell how this differs from shopify_list_orders or shopify_list_products beyond the resource name.

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?

There is no when-to-use guidance and no named alternative. The only conditional ('where the store's plan allows them') describes a constraint, not a selection rule, so the agent gets no help deciding when to call this versus another reporting or Shopify listing tool.

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