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

Adds substantial context beyond the annotations: it requires an API key, is ordered newest first, is private to the caller, has no rating effect, and most importantly discloses the read-receipt side effect ('Reading marks the rows read, once: read_at is the moment you first read each one') that the readOnlyHint alone would hide.

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-loads the core concept before the long clause enumerating returned fields. The density is largely justified because there is no output schema, but the proof-ladder expansion and layered parentheticals make it a heavy single block that could be trimmed.

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 fully documents the return shape (flags, proof ladder, counts, tx_hash, network, wallet, read_at, reply) and the two-way received/sent split, plus privacy and read-marking behavior. An agent has everything needed to call and interpret it.

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 both `limit` (per list, newest first) and `listing_id` (one listing vs all) are already documented. The description echoes the filtering behavior but adds no syntax or defaults the schema lacks; baseline 3 applies.

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+resource ('private feedback on your listings') and cleanly splits the tool's two modes: `received` (what agents sent you) and `sent` (what your wallet signed elsewhere). It distinguishes itself from review-oriented siblings by asserting 'nothing is public and nothing here moves a rating.'

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?

Gives the routing rule 'Answer one with replyToListingFeedback' and the condition for narrowing to one listing ('Pass `listing_id` for one listing'). Clear context, though it never states explicit exclusions such as when to prefer getFeedbackStatus or myReviews instead.

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