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

Annotations declare readOnlyHint=true, and the description is consistent with that plus adds real behavioral context: deleted listings are excluded, results are ordered newest first, and owner-supplied text fields are surfaced under `_untrusted`. It stops short of describing rate limits or auth failure behavior.

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 dense paragraph that front-loads ownership, ordering, and returned fields before pagination and the untrusted-data note. Information-dense with little waste, though the parenthetical stat list makes it slightly packed.

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 no output schema, the description carries the return-shape burden and does so well: item status values, sales count, seller stats, ordering, exclusions, and pagination are all covered. An agent has what it needs to call and interpret this tool.

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%, so both parameters are already documented (limit max 100, default 50; cursor from previous page). The description largely restates those facts, adding only the `next_cursor` naming link, so the baseline 3 is appropriate.

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 resource and scope: your own listings, newest first, with a named owner requirement (needs your API key). The ownership framing cleanly distinguishes it from siblings like getListing and search, which operate on listings generally.

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?

It routes edits to updateListing() and explains pagination, which implies the read use case, but never states when to use this versus alternatives such as search or getListing, nor any exclusions. Usage is inferable rather than explicit.

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