GetShippingOptions

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

No annotations are provided, so the description carries the full burden. It states the tool retrieves a list and mentions sorting/pagination, but lacks details on permissions, rate limits, error handling, or what the return format looks like (e.g., list structure, fields included). For a read operation with 8 parameters, this is insufficient behavioral disclosure.

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 concise and front-loaded, with the main purpose stated first. The two sentences are efficient, though the second sentence could be more polished (e.g., 'Shipping options can also be sorted or paginated'). There is no wasted verbiage, but it under-specifies given the tool's complexity.

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's complexity (8 parameters, no annotations, no output schema), the description is incomplete. It lacks details on parameter usage, behavioral traits, and output format. For a retrieval tool with filtering and pagination capabilities, more context is needed to guide effective use by an AI agent.

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 only explains the 'cart_id' parameter, leaving 7 other parameters (fields, offset, limit, order, $and, $or, is_return) undocumented. The description adds minimal value beyond the schema, failing to clarify the purpose or usage of most 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 purpose: 'Retrieve a list of shipping options for a cart.' It specifies the verb ('retrieve') and resource ('shipping options for a cart'), making the intent unambiguous. However, it does not explicitly differentiate from sibling tools like 'PostShippingOptionsIdCalculate' or 'PostCartsIdShippingMethods', which might handle related but different operations.

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 minimal guidance: it mentions that the cart's ID is required, but offers no advice on when to use this tool versus alternatives like 'PostShippingOptionsIdCalculate' (which calculates shipping) or 'PostCartsIdShippingMethods' (which might apply shipping methods). There is no explicit when/when-not or alternative usage context provided.

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