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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds genuine behavioral context beyond those hints: publication is a commitment to fulfill orders rather than a quality guarantee. This is useful interpretation of what the data means and cannot be derived from the schema or annotations.

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 sentences carry the entire definition: the first states the action and data fields, the second provides a crucial interpretive caveat. There is no filler, repetition, or padding.

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 simple read-only tool with two parameters and no output schema, the description gives enough to select and invoke it correctly: the action, the target resource, the fields to inspect, and a caveat about interpretation. A small gap is the unexplained term 'standard/Pro buyer totals,' but this is minor given the otherwise complete context.

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 50%: agent_key is described, but service_id has no schema description beyond its pattern. The description does not compensate by explaining service_id or how it identifies the standing service offer. It only describes the contents of the resource itself, leaving parameter semantics under-specified.

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 a specific verb and resource: 'Read the current version of a standing service offer before ordering.' It lists concrete contents (schemas, capacity, availability, price, buyer totals), making the tool's purpose clear. It does not explicitly name or contrast sibling tools, so it stops short of full differentiation.

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 phrase 'before ordering' gives a clear intended context, and the final sentence warns agents not to treat publication as proof of quality or runtime availability. However, it does not state when to use alternatives such as speedbot_exchange_services or speedbot_exchange_service_draft, nor does it give explicit when-not guidance.

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