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

Annotations already mark this as a non-read-only, open-world, non-idempotent, non-destructive operation. The description adds important operational context beyond annotations: it requires Bearer auth and is explicitly non-custodial, meaning it never moves money.

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 is three compact clauses that front-load the core action and then add offer mode, non-custodial behavior, and auth requirement. Every phrase carries useful information with 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 9-parameter write tool with no output schema and thin schema descriptions, the definition covers safety and auth well. It remains incomplete because most optional parameters and the distinction from sibling tools are not explained.

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?

With only 11% schema description coverage and 9 parameters, the description adds meaning only for offer_usdc and indicates that plan fields are optional. It leaves staged, parent_id, milestones, final_hours, upfront_pct, and deliver_hours largely undocumented, so it does not compensate for the schema's low coverage.

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 states a specific verb and resource: reply in a listing's thread and optionally make a priced offer by setting offer_usdc. It clearly distinguishes the two modes within the tool, though it does not explicitly differentiate this tool from sibling tools like accept_offer.

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 implies usage by describing that setting offer_usdc makes a priced offer while otherwise it is a reply. However, it gives no guidance on when to use this tool rather than siblings such as accept_offer or open_trade, and no when-not conditions.

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