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

Annotations already declare destructiveHint=true and openWorldHint=true; the description adds valuable context beyond them: bound wallet and explicit authorization to publish and fulfill matching orders without bidding, consent requirements, the 10% commission / 90% net split, and that existing orders keep their original terms despite replacement. It does not explain what the publish call returns or how request_id drives idempotency, which keeps it from a 5.

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?

It is a single dense paragraph that mixes the core action with bonus-campaign logistics, plan availability ("Available on every plan; Pro is optional"), and a vague trailing caveat ("This is guidance, not a minimum price") whose referent is unclear. Sentences like these dilute the front-loaded value, though the required-parameter checklist in the second sentence is efficient.

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 24-parameter destructive mutation with nested objects and no output schema, the description covers the critical agent decisions: consent flags, commission acceptance, edit versioning, capacity, and the bonus path. Missing are the shape of a successful response and any rate-limit or failure-mode guidance, which is a real but modest gap given the annotation coverage.

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 24 parameters at 33% schema coverage, the description compensates well for the highest-risk fields: accept_listing_commission:true, exactly one of delivery_minutes or delivery_hours, service_id plus expected_version for edits, listing_bonus:false opt-out, and the market_service_bonus sub-fields. Several parameters (tags, network, valid_for_hours, max_active_orders, offer_declaration, result_validation, request_id) receive no mention in either description or schema, so coverage is still incomplete.

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?

Opens with a specific verb and resource: "Publish or replace your own standing service offer," which an agent can map to a concrete write action distinct from read-oriented siblings like speedbot_exchange_read. The purpose gets somewhat diluted by campaign, bonus, and pricing commentary that follows, so the core action is clear but not maximally front-loaded.

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?

Explicitly routes the agent: "Use service_draft for prefilled contracts," "To edit/renew, include service_id and current expected_version," and "To apply for the targeted finance campaign supply market_service_bonus." It also defines when escrow applies (fixed tasks of about 5-50 USDC). It stops short of stating hard exclusions or prerequisites for the non-campaign path, so not a 5.

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