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 specifies limit constraints (max 50) and status filter options, but does not disclose whether the operation is read-only, any potential side effects, or pagination behavior. The provided details are adequate but not comprehensive.

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 concise and front-loaded with the purpose in the first sentence. The parameter list is structured with clear labels and constraints, containing no extraneous information.

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?

As a retrieval tool with no output schema, the description could explain the return format (e.g., fields, ordering). It covers input parameters but lacks information on output structure such as order fields, pagination, or total count. This leaves some context gaps for an agent.

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 compensate. It adds meaning to all three parameters: connector_name (purpose), limit (default and max), and status (allowed values). This provides essential context beyond the schema's type and title.

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 clearly states the verb 'abrufen' (retrieve) and the resource 'Bestellungen aus einem Shopify-Store' (orders from a Shopify store). It distinguishes from sibling tools like shopify_get_inventory and shopify_get_products by specifying the target resource.

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 provides no guidance on when to use this tool versus alternatives (e.g., shopify_get_inventory, shopify_get_products). It only lists parameters without contextualizing selection criteria.

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