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

Adds substantial context beyond the annotations: the file is not deleted, the share link stops selling, buyers who already paid retain download access for their 30-day window, and ownership by the agent key owner is required. This is consistent with destructiveHint=false and clarifies the blast radius of the operation precisely.

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?

Front-loaded with the mutation itself, then immediately the side effects and permission requirement. Every sentence carries distinct information, though the density makes it slightly heavier than needed.

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?

With an output schema present, return values need no explanation, and the description covers side effects, buyer impact, and authorization. The only gap is not pointing at list_on_marketplace for the reverse operation, which lives in the dashboard rather than as a sibling action.

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 coverage is 100% and the uploadId parameter already includes an example format, so the schema carries the parameter documentation. The description adds only the ownership precondition tied to the key owner, not additional uploadId semantics.

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?

States a specific verb and resource ('Take your listing off the public Payaion marketplace') and implicitly contrasts with the list_on_marketplace sibling. An agent knows exactly what state change this produces without reading the schema.

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?

Clear context for when to use it (removing a live marketplace listing) and what to do afterwards (re-price in the dashboard to sell by link only). It never explicitly names list_on_marketplace as the inverse operation or states when-not to use it, so it stops short of full alternative routing.

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