store_create_shipping_rate

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

Annotations indicate this is not read-only, not idempotent, and not destructive, which covers basic safety. The description adds no behavioral traits beyond the verb 'Create', such as side effects, required existing entities, or response behavior. It doesn't contradict annotations but contributes little beyond what annotations already imply.

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?

At three words, it is extremely concise and front-loaded, but it may be under-specified for an operation with 14 parameters. It is not verbose or unstructured, but it also doesn't provide any context that would warrant a higher score for conciseness. The brevity is acceptable for a simple create, but lacks substance.

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 14 parameters, 8 required, and no output schema, the description provides no overall context about shipping rate creation, such as the relationship between conditions, carrier rates, or typical use. The schema helps per-parameter, but the tool description leaves the agent without a high-level understanding of the operation's purpose and constraints. Incomplete for a complex creation endpoint.

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 all 14 parameters are described in the input schema. The tool description itself adds no parameter information, but since the schema fully documents each field, the baseline is 3. There is no additional semantic enrichment from the description.

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 Shipping Rate' clearly states the action (create) and the resource (shipping rate). It distinguishes the tool from update/delete rate operations by the verb, though it doesn't explicitly differentiate from siblings with similar naming. The purpose is unambiguous and matches the tool name, which is slightly tautological but still informative.

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, prerequisites (e.g., existing shipping zone, carrier), or how it compares to alternatives like store_update_shipping_rate or store_create_shipping_carrier. There is no context about scenarios that warrant this tool over others. The description is entirely silent on usage.

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