edit_marketplace_order

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

With no annotations, the description carries full burden but only says 'Edit a marketplace order'. Fails to disclose side effects (e.g., it modifies the order status in the system), authorization requirements, or potential irreversible actions.

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 very concise (one sentence), but at the cost of omitting critical information. It could be improved by adding a brief explanation of parameters and usage while staying brief.

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 this is a mutation tool with 3 parameters (one with an enum of 10 values), the description is incomplete. It does not explain return values, required permissions, or constraints on status transitions, making it insufficient for correct invocation.

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 description adds no meaning beyond the schema; it does not mention parameters at all. Schema coverage is 0%, so the agent gets no help understanding the status enum semantics or the meaning of the shipping field.

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 tool edits a marketplace order, distinguishing it from read-only tools like get_marketplace_order and other actions like create_marketplace_listing. However, it does not specify which 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 is provided on when to use this tool versus alternatives, such as when to edit an order versus creating a new order or cancelling one. Lacks context about required order states or prerequisites.

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