PostOrdersIdTransferDecline

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 the tool declines a transfer and references an admin API route, but doesn't specify required permissions, whether the action is reversible, rate limits, error conditions, or what happens upon success. This leaves significant gaps for a mutation tool.

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 purpose and context. It's appropriately sized without unnecessary details, though it could be slightly more front-loaded by stating the action more directly at the beginning.

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?

For a mutation tool with no annotations, no output schema, and 2 undocumented parameters, the description is insufficient. It lacks details on permissions, behavioral outcomes, parameter usage, and error handling, making it incomplete for safe and effective agent use.

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, fields) with 0% description coverage, meaning they are undocumented in the schema. The description doesn't explain what these parameters represent, their expected formats, or how they're used in the decline operation. This fails to compensate for the low schema coverage.

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 ('Decline an order transfer previously requested') and identifies the resource ('order transfer'), making the purpose unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'PostOrdersIdTransferAccept' or 'PostOrdersIdTransferCancel', which would be needed for 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 provides some context by mentioning that the transfer was 'previously requested' and referencing the admin API route, which implies this is used after a transfer request exists. However, it doesn't explicitly state when to use this tool versus alternatives like 'PostOrdersIdTransferAccept' or 'PostOrdersIdTransferCancel', nor does it provide clear exclusions or prerequisites.

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