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

Adds value beyond the annotations: it discloses the realistic scope of destruction (removal from every list that holds the listing, not just one) and the sign-in requirement, neither of which is in the annotation block. It notably implies the listing itself is not deleted, only its shortlist membership – useful nuance the destructiveHint alone would not convey.

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?

A single tight sentence that front-loads the action, then the parameter-driven scope, then the auth note last. No wasted words, no redundancy with the schema or title.

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?

Covers the key agent needs: what is removed, the two scopes, and the auth requirement, with annotations already carrying the safety profile (destructive, idempotent). No output schema exists and none is needed, though success/failure behavior on a non-member listing is left to the idempotent annotation.

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 only 50% schema coverage, the description compensates by explaining the default behavior when `list` is omitted (remove from all lists), which the schema ('Only this shortlist. Optional.') does not state. The `id` parameter remains undocumented in both, but its meaning is self-evident.

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?

Specific verb+resource: 'Take a listing out of the person's shortlists' clearly states the operation on the shortlist resource, setting it apart from delete_saved_search (a different resource) and save_listing (the inverse). It never names a sibling explicitly, but the resource alone is unambiguous.

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 clarifies the two operating modes ('out of the named `list`, or out of every list of theirs that holds it') and adds an auth prerequisite, which is genuine usage context. However, it gives no explicit when-to-use vs. save_listing or when-not guidance and leaves routing to alternatives to inference.

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