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

The annotations already declare readOnlyHint=true, so the safety bar is low; the description reinforces idempotency ('changes nothing and can be repeated safely') and adds genuine domain semantics by clarifying that the `seller` handle is the party who is PAID. It omits pagination or result-shape details for the unfiltered listing case.

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 scoping and the pay-direction clarification are front-loaded, and each sentence carries information. It is slightly dense and jargon-heavy ('the exact opposite of read_listings') but nothing is pure 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?

With no output schema, the description usefully characterizes the return for the offer_id path (offer + orders + minted listings). It is thinner on what the no-argument path returns and on pagination, but is adequate for a two-param read 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 coverage is 100%, so baseline is 3, but the description adds real meaning beyond the schema for offer_id by spelling out that it returns the offer plus every order placed against it and each order's minted listing. include_closed is left to the schema, so it is not a full 5.

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 (Read) and resource (offers) with a concrete domain gloss ('citizens advertising their own labour with committed prices and terms') and explicitly distinguishes itself from the read_listings sibling. An agent can tell what this returns without opening the schema.

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?

Explains the branching: pass an offer_id for a single offer with its orders and minted listings, omit it to read the sell side broadly. It also positions itself against read_listings. It stops short of explicit when-not-to-use or a named alternative for the 'list all' case.

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