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

With no annotations, the description carries the full burden and does substantial work: it discloses the free tier and its per-wallet daily cap, the auth/identity requirement (caller keys the allowance), and crucially that it performs no network fetches and produces no grades. That is exactly the kind of behavioral context an agent needs to know this is a safe, cheap, non-authoritative call. It stops short of saying what a failed pre-check looks like or whether it errors.

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?

Two dense clauses, front-loaded with the FREE headline and the quota, then immediately the key caveat about what it does not do. No wasted words.

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 5-parameter tool with nested objects and no output schema, the description should sketch the return shape (e.g. per-op missing/incomplete fields, a pass flag). It says only 'assessability only', which conveys intent but leaves the agent guessing what it will actually receive back.

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 80% and the schema itself documents caller, listing, payload, and facilitator in detail. The description's only real addition is the op-dependent requirement logic ('complete for its op'), which signals that different ops need different subsets of listing/payload/facilitator. Useful, but thin over an already well-documented schema.

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 ('listing pre-check') and clarifies the scope precisely: it returns assessability only, fetches nothing, and grades nothing. That distinguishes it from the heavier listing_check_check / listing_check_bazaar siblings by implication, though it never names them.

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?

Cost and quota context (FREE, 100/day per wallet, pass caller) hint that this is the cheap gate to run before a full check, and 'returns assessability only' implies the before/after ordering. But there is no explicit when-to-use / when-not-to-use statement or named alternative, so the agent has to infer the routing.

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