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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds little behavioral context beyond the broad data categories: it does not mention pagination behavior, PII implications of include_pii, workspace/connection requirements, or filter behavior, which matter for a nine-parameter tool with nested filters.

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 a single front-loaded sentence with no wasted clauses, and the core read operation is immediately visible. The phrase 'and more' is vague, but the overall structure is efficient and appropriately short for a routing description.

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 tool with nine parameters, a thirty-value resource enum, nested filters, a PII toggle, and connection variants, the description is far too sparse to guide correct invocation. Annotations cover the read-only safety profile, but the description leaves nearly all operational complexity undocumented.

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 0%, so the description must explain the nine parameters, but it only vaguely gestures at resource categories. It does not explain required workspace/resource, how id differs from filters, pagination via first/after/response_cursor, the purpose of include_pii, or the shopify_connection union.

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 uses a clear verb ('Read') and resource ('connected Shopify store') and names major data categories such as orders, customers, products, inventory, and discounts. It is understandable in isolation, but it does not distinguish the tool from siblings like shopify_query, orders_get, or customers_get, so the agent has no basis for preferring this catch-all over a more specific reader.

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 states only that it reads Shopify data; it gives no when-to-use guidance, no exclusions, and does not mention alternatives such as shopify_query or resource-specific getters. It implies a general read operation but leaves the agent to infer when this tool is the right choice.

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