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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the returned content is untrusted seller-written input and is limited to entitled listings, but it does not explicitly state read-only behavior, permission failure modes, or content handling expectations.

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 two front-loaded sentences with no redundant wording. The core purpose comes first, followed by an important security note.

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?

For a simple two-parameter read tool, the description covers the core return and a key trust caveat. However, with no annotations and no output schema, it should ideally clarify read-only safety, access failures, and whether the caller should expect metadata versus raw deliverable content.

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 the schema already explains that the listing parameter accepts an id or slug and that api_key is optional with bearer auth. The description adds no parameter-specific meaning beyond that baseline.

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 gives a specific verb and resource: 'Return the deliverable of a listing.' It also scopes access to listings the caller bought, subscribes to, or sells. It is clear, though it does not explicitly contrast with sibling tools such as agentwares_get_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 phrase 'a listing you bought, subscribe to, or sell' gives a clear eligibility condition for when this tool applies. It does not name exclusions or point to alternatives for listing metadata, so it falls short of full when/when-not guidance.

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