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. The description adds real value by disclosing data provenance ('synced from Shopify') and the returned field set, but says nothing about pagination behavior, result caps, or the GET /vendor/order endpoint's practical constraints beyond naming it.

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, front-loaded with the resource and its returned fields, then the filter options. The '(e.g. #1001)' duplicates the schema's example and the trailing 'GET /vendor/order' is of marginal use to an agent, but the text is dense with little waste.

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 read-only list tool with no output schema, the description compensates well by enumerating the returned fields, so an agent can predict the response shape without an output schema. Pagination and sorting are handled in the schema, leaving no major gap.

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 page, page_size, sort, order_label, processed_after and processed_before are all fully documented in the schema. The description only restates the two filter parameters without adding syntax or format detail, so 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 ('List orders Smartrr has synced from Shopify') and enumerates what each order carries (totals, status, fulfillment status, tracking, items, customer), so an agent knows exactly what comes back. It distinguishes list-scope from the single-record sibling smartrr_get_order only implicitly via the 'filter by order label' hint, rather than naming it.

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?

Usage is implied — 'List orders ... Filter by processed date or order label' tells the agent this is the browse/filter entry point. It never states when to prefer smartrr_get_order for a single order, or when to use the more targeted smartrr_get_subscription_orders, so the routing decision is left to inference.

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