Medusa MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that the transfer requires confirmation via another API, which adds useful context about the workflow. However, it doesn't cover critical aspects like required permissions, potential side effects (e.g., order status changes), error conditions, or response format, leaving 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 concise with two sentences that directly address the tool's purpose and next steps, with no wasted words. It's front-loaded with the main action, though it could be slightly more structured by explicitly separating purpose from guidance.

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 (a mutation with 2 undocumented parameters, no annotations, and no output schema), the description is incomplete. It covers the basic purpose and hints at a confirmation step but misses details on parameters, behavioral traits (e.g., auth needs, effects), and return values, making it inadequate for reliable 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 and fields) with 0% description coverage, meaning they are undocumented in the schema. The description doesn't explain what these parameters represent (e.g., that 'id' is the order ID or what 'fields' controls), failing to compensate for the low schema coverage. This leaves the agent guessing about parameter meanings and usage.

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 ('Request an order to be transfered') and the target ('to the logged-in customer's account'), providing a specific verb and resource. However, it doesn't explicitly differentiate from sibling tools like PostOrdersIdTransferAccept, PostOrdersIdTransferCancel, or PostOrdersIdTransferDecline, which all relate to order transfers but serve different purposes.

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 by referencing the logged-in customer and linking to the Accept Order Transfer API for confirmation, suggesting this is an initial request step. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., when to choose transfer over cancellation or decline), and doesn't mention prerequisites or exclusions, leaving some context implied rather than stated.

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