store_create_store_setting

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

Annotations already signal that this is a write operation (readOnlyHint=false) and non-idempotent (idempotentHint=false). The description 'Create/Update' merely confirms mutation but adds no detail about whether it is an upsert, whether it replaces or merges settings, required permissions, or potential side effects. It fails to disclose any behavioral nuances beyond what the annotations state, so it adds little value.

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 a single, succinct sentence, which is concise, but it is under-specified. It lacks critical context about which settings are affected and how they behave. While there is no verbosity or waste, the minimalism reduces its usefulness. It is appropriately short but not effectively informative.

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 the tool has 5 parameters with nested objects (shippingOrigin, two notification configurations) and no output schema, the one-line description is insufficient. It does not explain that it configures the store's shipping origin and order/fulfillment notification emails, nor does it mention defaults for altId/altType. An agent lacks the context needed to understand the tool's full purpose and requirements beyond the schema.

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%—every property like shippingOrigin, storeOrderNotification, and altId has a description. The tool description itself does not mention any parameters or add meaning to them. Per calibration, a baseline of 3 is appropriate when the schema fully documents parameters, and the description offers no additional semantic value.

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 'Create/Update Store Settings' clearly indicates a mutation of store settings with a specific resource. It distinguishes itself from other store tools like carrier/shipping-zone managers, but does not explain what 'settings' specifically include (e.g., shipping origin, order notifications). It is not tautological and conveys a clear verb+resource, though it could be more explicit about the scope.

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. It does not mention any exclusions, prerequisites, or sibling tools (e.g., store_get_store_settings, store_update_shipping_carrier). An agent receives no context about appropriate scenarios or limitations, leaving usage entirely to inference.

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