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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotency are covered structurally. The description adds one genuinely new fact, 'No auth', which is useful for call planning. It says nothing about page size behavior, result ordering, or what a listing contains.

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?

Three short fragments, front-loaded with the when-condition and ending in a call example. The redundant 'Barter list.' opener is the only wasted element; everything after it earns its place.

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?

The tool is simple (2 optional params, no nesting), and the description covers when to use it and the auth situation. With no output schema, though, an agent has no idea what a listing record looks like or whether results are paginated, which leaves a real gap for a browse 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 description coverage is 100%, so both `limit` and `status` (with its enum) are already documented in the schema. The description adds only the empty-object example, which signals that no parameters are required — real but minimal added meaning.

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 and resource ('browse open CASH market broker listings') and scopes it against one sibling domain ('not token bazaar'), so an agent can distinguish it from bazaar_browse_listings. The leading 'Barter list.' only restates the title, but the rest of the sentence carries the real purpose.

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 'WHEN:' clause gives an explicit trigger condition and an explicit exclusion (not the token bazaar). It stops short of naming the token alternative that should be used instead, which keeps it from a 5.

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