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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered externally. The description adds only the underlying endpoint path; it says nothing about pagination behavior, empty results, or ordering of returns beyond what the schema's sort/page fields imply.

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?

Two sentences, zero filler, with the scoping qualifier front-loaded before the endpoint path. Nothing in it is redundant with the title.

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 simple read-only list tool with a fully documented schema and no output schema, the description is nearly sufficient: 'orders generated by one subscription' conveys the return shape at a coarse level. It falls short only in not hinting at the order fields returned or pagination continuation beyond the schema's next_page reference.

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%: page, page_size, sort, and shopify_subscription_id are each documented in the schema, including the default and max values and the cross-reference to smartrr_list_subscriptions. The description's mention of the Shopify subscription id adds no meaning beyond that, so the 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 (list) and resource (orders) with a clear scope: orders belonging to one subscription, keyed by Shopify subscription id. That scope implicitly separates it from smartrr_list_orders (all orders) and smartrr_get_order (a single order), though neither sibling is named.

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 scope phrase 'Orders generated by one subscription' implies when the tool is appropriate, but there is no explicit when-to-use vs. use-smartrr_list_orders guidance and no stated prerequisites (e.g., whether the subscription must be active). Usage must be inferred rather than read.

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