PostOrdersIdTransferCancel

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions that the action is a cancellation and that it applies to a previously requested transfer, but lacks details on permissions required, side effects (e.g., whether the transfer is reversible after cancellation), error conditions, or response format. This is inadequate for a mutation tool with zero annotation coverage.

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, well-structured sentence that efficiently conveys the core action and context without unnecessary words. It could be slightly improved by front-loading more critical details (e.g., parameter hints), but overall it's appropriately concise.

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 as a mutation with 2 undocumented parameters, no annotations, and no output schema, the description is insufficient. It lacks essential details about behavior, parameters, and expected outcomes, making it incomplete for effective agent use. The reference to another API route adds some context but doesn't fill these gaps.

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?

The input schema has 2 parameters (id and fields) with 0% description coverage, meaning neither parameter is documented in the schema. The description provides no information about what these parameters represent, their formats, or how they should be used, failing to compensate for the schema gap. For example, it's unclear if 'id' refers to the order ID or transfer ID, or what 'fields' does.

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 ('Cancel') and resource ('an order transfer that the logged-in customer previously requested'), making the purpose specific and understandable. However, it doesn't explicitly distinguish this tool from its sibling 'PostOrdersIdTransferDecline' which might serve a similar cancellation purpose, preventing a perfect score.

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 implies usage context by referencing that the transfer must have been 'previously requested' and by linking to the request API route, providing some guidance. However, it doesn't explicitly state when to use this tool versus alternatives like 'PostOrdersIdTransferDecline' or other order management tools, leaving room for ambiguity.

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