edit_marketplace_order

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

The description omits behavioral details like side effects (e.g., whether editing order status triggers notifications or is destructive), permissions required, or irreversible actions. The input schema hints at cancellations but the description does not clarify.

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 concise sentence, but it sacrifices necessary detail. It is front-loaded with the core purpose but insufficient for effective tool use.

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 lack of annotations, output schema, and parameter documentation, the description is incomplete. It does not explain return values, field constraints, or ordering context, forcing the agent to guess.

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?

With 0% schema description coverage, the description adds no clarification for the three parameters. The enum status values and shipping field (currency? units?) are unexplained, leaving the agent uncertain about valid inputs.

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 'Edit a marketplace order' clearly identifies the verb (edit) and resource (marketplace order), distinguishing it from read (get_marketplace_order), creation (create_marketplace_order_message), and other sibling tools. However, it is generic and does not specify what fields can be edited.

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?

No guidance on when to use this tool versus alternatives, such as get_marketplace_order for reading or create_marketplace_listing for new listings. No prerequisites or context about valid order states for editing are provided.

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