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

With no annotations provided, the description carries the full behavioral burden, and it does so thoroughly: it declares read-only/no side effects, details the return shape, explains the no_offer_reasons behavior, warns about expiry, and discloses that seller_signature cannot currently be verified. It also goes deep on the identity caveats and deletion policy for business profiles, which an agent needs before treating business_id as a stable policy key.

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 description front-loads the core purpose and usage, then systematically covers return shape, expiry, identity caveats, and security limitations. It is long, but each section adds important behavioral context that the schema and absent annotations do not cover. Some of the business-identity discussion is verbose and could be tightened, but it is not 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?

Despite having no output schema and no annotations, the description is exceptionally complete for this tool: it covers workflow position, required input provenance, return shape, empty-result behavior, expiry implications, and a hard limitation about signature verification. It gives the agent everything needed to call list_offers correctly and interpret its results safely.

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%, and the schema already documents all envelope parameters in detail, so the baseline is 3. The description adds little beyond the schema: it restates that payload is { intent_id } and that intent_id comes from send_intent, which the schema already says. No parameter semantics beyond the schema are provided.

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 opens with 'STEP 3. Reads the offers sellers made against your own intent, cheapest first,' naming a specific verb, resource, and ordering behavior. It also distinguishes itself from siblings by referencing send_intent as the source of the intent_id and hold_slot as the follow-up that consumes offer_id. The scope is unambiguous: list offers on your own intents only.

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 description states the tool is STEP 3 in a workflow, requires an intent_id returned by send_intent, and notes it only works on intents your own agent created. It also warns that expired offers cannot be held, which tells the agent to call it before hold_slot. It does not explicitly name alternatives or say when not to use this tool, but the sequencing and constraints are clear enough.

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