shopify_get_orders

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

No annotations are provided, so the description carries full burden. It mentions 'List orders with filters', which implies a read-only operation, but doesn't disclose behavioral traits like rate limits, authentication needs, pagination behavior, or what happens with no filters. For a tool with zero annotation coverage, this leaves significant gaps in understanding its operation.

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 extremely concise with a single sentence 'List orders with filters.', which is front-loaded and wastes no words. Every part earns its place by stating the core action and capability efficiently.

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?

Given complexity (3 parameters, no annotations, no output schema, and low schema coverage), the description is incomplete. It doesn't explain return values, error handling, or usage context, making it inadequate for an agent to invoke the tool correctly without additional assumptions.

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 33% (only 'customerId' has a description), so the description must compensate but adds minimal value. It mentions 'filters' generically, which aligns with the parameters but doesn't explain semantics beyond what the schema provides (e.g., how 'status' enum values affect results). Baseline is 3 due to low coverage, but the description doesn't fully compensate for undocumented parameters like 'limit'.

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 'List orders with filters' clearly states the verb ('List') and resource ('orders'), but it's vague about scope and doesn't distinguish from sibling tools like 'shopify_get_customer' or 'shopify_get_products'. It specifies filtering capability but lacks detail about what 'list' entails (e.g., pagination, date ranges).

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?

No guidance on when to use this tool versus alternatives like 'aiva_search_customers' or other Shopify tools. The mention of 'filters' implies it's for filtered queries, but there's no explicit context, prerequisites, or exclusions provided to help an agent choose appropriately.

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