shopify_bulk_export_start

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

The description calls the export 'read-only', but annotations state readOnlyHint=false and destructiveHint=true. This is a direct annotation contradiction. The description also does not disclose side effects, authorization requirements, or what happens after starting the export.

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 compact and front-loaded: it states the operation in the first sentence and the essential follow-up (save the operation ID) in the second. It wastes no words, though the misleading 'read-only' claim harms precision.

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 an asynchronous start command with three required parameters and no output schema, the description omits needed context: what query syntax to use, what 'store' expects, the confirmation/authorization step, and what the operation ID looks like. The annotation contradiction further undermines completeness.

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 low (33%), with only 'confirm' documented. The description does not explain 'query', 'store', or the confirmation requirement, so the agent is left without semantic guidance for most required parameters.

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 names a specific action ('Start an asynchronous... bulk export') and resource (Shopify bulk export), and it tells the agent to save the returned operation ID. It does not explicitly name sibling alternatives, but the action is distinguishable from status/query tools.

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 is given about when to choose this tool over alternatives such as shopify_bulk_export_status or direct GraphQL queries. The only context is that it is asynchronous and the ID should be saved, which implies but does not state a usage pattern.

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