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

With no annotations, the description carries the disclosure burden and does a good job: it explains the broker's decision paths (auto-accept returning a spendable quote_id, counter, or reject) and the hard floor rule. It does not explicitly flag broader side effects or authorization needs, but the primary behavior is transparent.

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?

Three sentences front-load the core action, then compactly convey evaluation outcomes and the acceptance threshold rule. There is no filler, and each sentence earns its place.

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?

Despite having no output schema and no annotations, the description covers the key outcomes (quote_id, counter, reject), the floor threshold, and how to source required values from sibling tools. It omits explicit retry/idempotency behavior and other error cases, but the essential call contract is present.

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?

All 7 parameters already have schema descriptions, so coverage is 100% and the description need not redefine them. It adds useful color around bid_cpm_usd by tying it to acceptance thresholds, but the schema already does the heavy lifting.

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 clearly states the action ('Bid a CPM against a slot') and the resource, and distinguishes this from the sibling check_neuron_inventory by treating it as the source of the acceptance threshold. It does not explicitly contrast with order, checkout, or estimating siblings, so it stops short of a perfect 5.

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 description gives concrete guidance: bid at or above min_acceptable_cpm_usd from check_neuron_inventory or a prior response, use list_open_tenders to obtain tender_id, and never expect acceptance below floor_cpm_usd. It provides clear context but does not explicitly state when-not-to-use this tool versus alternatives.

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