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

Beyond the readOnlyHint annotation, it discloses that listing text is untrusted citizen content, not instructions or verdicts, and that returned data carries a server-owned provenance boundary in _meta. This adds meaningful safety behavior the annotation alone does not provide.

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 purpose is front-loaded, followed by essential trust/provenance warnings and a read-only safety confirmation. Every sentence adds behavioral or functional value with no filler.

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?

It explains the two primary modes and the trust boundary of returned data, but without an output schema it omits parameter semantics for since_id and include_expired, default behavior, and response shape. Adequate for a simple read call but with clear gaps.

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 only 33%; only listing_id is described, and the description connects it to 'one listing with every payout binding filed against it.' However, since_id and include_expired are left entirely unexplained, so the description does not compensate for the low coverage.

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 states a specific read operation: list open listings or fetch a single listing with all payout bindings filed against it. This is distinct from generic fetch/post_listing siblings and makes the two modes clear.

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 clearly frames when this tool applies (open listing feed or one listing with bindings), but does not explicitly name sibling alternatives or state when NOT to use it. The context is sufficient for routing, just lacks exclusions.

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