Set listing discount (PAID/impactful)

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

Description adds context beyond annotations: it reveals the temporary nature of the discount and that it changes the live price, which aligns with 'destructiveHint: true'. No contradictions with annotations.

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?

Two concise sentences, front-loaded with the action and endpoint. No unnecessary words, but could be slightly more structured.

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?

Lacks information about prerequisites (e.g., listing must exist and not already have a discount), expected outcome or return value (no output schema), and error conditions. Adequate for a simple tool but incomplete given the destructive nature.

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?

All three parameters have descriptions in the schema (100% coverage), so the description adds minimal extra meaning beyond the schema. Merely mentions 'temporary discounted price' which is already implied by the price parameter.

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?

Clearly states the action 'Set a temporary discounted price' on a listing, and mentions the HTTP endpoint and impact on live price. However, it does not explicitly distinguish from the sibling 'finish_listing_discount'.

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?

Includes an important instruction 'Confirm with the user first,' indicating a conversational prerequisite. However, it lacks guidance on when to use versus alternatives or any conditions for use (e.g., listing must not already have a discount).

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