Create store

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

Annotations already mark this as a write operation (readOnlyHint=false, destructiveHint=false). The description adds a meaningful side effect — a primary sales channel is auto-created — but does not disclose other behavioral details such as store limits, naming constraints, or whether creation is immediate or asynchronous.

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 short sentences, both informative. The first states the operation and scope, and the second adds a relevant side effect. No filler or redundancy.

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 create operation with six parameters, a nested sales_channel object, an empty required array, and no output schema, two sentences are insufficient. The agent is not told which parameters are effectively required, what a successful response contains, or what creating a primary sales channel implies for further setup.

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 the baseline applies. The description adds no parameter-level meaning beyond the schema, and several schema parameter descriptions are tautological ('name parameter', 'company_name parameter'), so there is no bonus for clarity.

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 states a clear verb and resource: 'Create a new store for your account.' It also mentions that a primary sales channel is created, which helps distinguish it from sales-channel-specific tools. However, it does not explicitly name an alternative, so it stops short of full sibling differentiation.

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 on when to use this tool versus related siblings such as ecommerce_createASalesChannelV1, ecommerce_getStoresV1, or ecommerce_updateSalesChannelV1. There are no prerequisites, exclusions, or decision criteria for choosing this tool.

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