PostShippingOptionsIdCalculate

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

No annotations are provided, so the description carries full burden. It mentions 'Calculate' but doesn't disclose behavioral traits such as whether this is a read-only operation, if it requires authentication, potential side effects (e.g., updating cart state), rate limits, or error handling. This leaves critical operational details unspecified for a tool that likely interacts with cart data.

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, direct sentence with no wasted words, effectively front-loading the core purpose. It's appropriately sized for a simple tool, though its brevity contributes to gaps in other dimensions like guidelines and parameter details.

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 complexity (a calculation tool with 2 parameters), no annotations, 0% schema coverage, and no output schema, the description is incomplete. It fails to explain parameters, behavioral context, or return values, leaving the agent with significant uncertainty about how and when to use this tool effectively in the broader cart and shipping workflow.

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 0%, so the description must compensate. It doesn't explain the 'id' (e.g., cart ID, shipping option ID) or 'fields' parameters, their formats, or required values. Without this, the agent lacks essential context to invoke the tool correctly, making the description insufficient for the two undocumented 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 clearly states the action ('Calculate') and resource ('price of a shipping option in a cart'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'PostCartsIdShippingMethods' or 'GetShippingOptions', which might handle related shipping operations, leaving some ambiguity about its specific role.

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. With siblings like 'PostCartsIdShippingMethods' (which might set shipping methods) and 'GetShippingOptions' (which might list options), there's no indication of prerequisites, context (e.g., after adding items to a cart), or exclusions, relying solely on the agent to infer usage.

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