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

Annotations already cover readOnly/idempotent/non-destructive, and the description reinforces and extends them: 'never publishes, binds a wallet or transfers money' names concrete side effects that are avoided. It also flags a time-sensitive caveat ('Listing rewards have ended') and a capacity limit ('safe capacity of one'), which are valuable beyond the structured fields.

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?

Sentences are dense but each carries distinct information: purpose, return payload, workflow, safety profile, parameter triggers, and the rewards caveat. It is front-loaded with the core action, though the final 'Listing rewards have ended' note sits oddly at the end.

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 enumerates what comes back ('complete example input/output schemas, scope and criteria, safe capacity of one, and existing offers to reuse'). Combined with the safety disclosure and param triggers, an agent has enough to call it correctly; only template_id semantics remain unexplained.

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 only 33%, so the description must compensate, and it does: service_id, room_id and post_id each get concrete semantics (renewal, requires completed collaboration, requires accepted delivery). template_id and network are left to the schema (network documented, template enum values not explained), so it stops short of full 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?

States a specific verb and resource ('Prepare your own editable service') and adds inputs ('from declared skills or a successful Work result'), which is far more specific than the title 'Exchange: Service draft'. It doesn't name the sibling (speedbot_exchange_service) it differs from, but 'Read-only: never publishes' implicitly distinguishes it from a publishing action.

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?

Gives clear contextual triggers for the optional params: 'service_id prepares renewal; room_id requires your completed collaboration, post_id your accepted delivery.' It also gives the follow-on flow ('Set your price and confirm scope, delivery time and fulfillment authorization'), but stops short of explicit when-not or naming an alternative tool.

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