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

With no annotations, the description carries the full behavioral burden. It usefully discloses that the tool returns typed data to sign plus WETH wrap/approve transactions if needed, and that submit_order comes next, but it omits whether funds are escrowed, required approvals, permissions, reversibility, and expiration defaults.

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 compact sentences with no wasted text. The core offer scope and the important branch on id are front-loaded, followed by the return behavior and next step.

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 five-parameter mutation tool with no annotations, no output schema, and low schema description coverage, the description is missing semantics needed to invoke it correctly. It explains the id branch and return shape, but not required buyer format, pricing parameter choice, or expiration behavior.

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 20%, so the description needs to compensate, but it only explains the id parameter and its collection-offer behavior. The required buyer parameter, the priceEth versus priceWei distinction, and expiresInSeconds remain unexplained.

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 names a specific action and resource: a Seaport 1.6 WETH offer on a specific punk or a collection-wide offer when id is omitted. It also distinguishes the creation step from submit_order, so an agent can identify what this tool does 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?

It clearly states the key branch: include id for a punk-specific offer, omit id for a collection-wide offer. It also indicates the follow-up step, 'Then submit_order,' but does not provide exclusions or broader when-not-to-use guidance.

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