shopify_bulk_operation_create

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

Discloses asynchronous behavior and polling mechanism, but contradicts itself by labelling query as 'required' in description while schema shows it as optional with default null. No mention of side effects, rate limits, or error handling.

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 action, then return value and next step. No extraneous words.

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?

With output schema present, return value is adequately described. However, parameter contradiction and lack of query syntax guidance leaves gaps. Adequate but not complete.

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?

Adds 'Bulk-operation GraphQL query (Shopify bulk-operation syntax)' which gives some semantics, but falsely claims the parameter is required when schema allows null. Schema coverage is 0%, so description should compensate but does so poorly.

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?

Specifies verb 'Submit' and resource 'Shopify bulk-operation query'. Mentions return of ID and reference to sibling tools for polling, distinguishing it from shopify.bulk_operation_status and shopify.bulk_operation_result.

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?

Describes when to use (submit bulk query) and what to do after (poll via status tool). Provides clear context but no explicit when-not-to-use or alternatives.

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