marketplaceAddOrModifySale

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 explaining behavior. While it identifies the action as create/update/cancel and notes domain ownership, it does not disclose potential side effects, whether updating overwrites existing sale settings, cancellation behavior, fee implications, or authentication requirements. For a mutation tool this is a significant transparency gap.

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 front-loaded sentence that efficiently names the operation, resource, and ownership prerequisite, plus a documentation link. It is concise without wasted words, though the terseness does limit the behavioral and usage guidance it provides.

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?

This is a complex tool with 18 parameters, three distinct actions, and no output schema or annotations. The description only provides a high-level summary and a link, leaving the agent to infer which parameters are relevant for each action and what the response/effects will be. Given the complexity, the description is not complete enough.

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?

Schema description coverage is 100%, so every parameter already has an individual description. The tool description itself adds no additional parameter-level meaning, such as which parameters apply to add versus modify versus cancel actions. Baseline 3 is appropriate because the schema handles the heavy lifting.

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 creates, updates, or cancels a Marketplace sale for a domain the user owns. This is a specific verb+resource combination that distinguishes it from sibling tools like marketplaceActiveSalesOverview, listAuctions, and bidAuction, which cover viewing or bidding rather than managing a listing.

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 gives useful context ('for a domain you own') and an API reference link, but it does not explicitly say when to prefer this tool over related siblings, nor does it mention exclusions or alternatives. The usage context is 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.