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

Adds substantial context beyond the annotations: per-stage pricing ($15 each), separate invoices per stage, non-atomic charging, no automatic transfer, and that already-completed stages remain consumed if a later stage fails. That failure/billing semantics is exactly the kind of thing annotations (readOnly=false, destructive=true, idempotent=true) cannot express, and it is consistent with the destructive/openWorld hints.

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?

Four short sentences, front-loaded with purpose, then sequence, then billing caveats. No filler; every sentence carries a distinct constraint an agent needs before calling.

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 paid, destructive, five-parameter nested workflow with no output schema, the description covers sequencing, cost ceiling, partial-failure billing and consent expectations well. The gap is return behavior — nothing says what the evaluation stage produces (scores, ranking, disqualification report) — which matters when there is no output schema to fall back on.

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 60% and the nested stageInputs fields are already well documented in-schema. The description adds real value on cost/authorization semantics (per-stage $15, own invoice per stage), which speaks to maxChargeUsd and paymentInvoiceIds, but it says nothing about idempotencyKey, consentExternalProcessing, or the uuid shape of paymentInvoiceIds — the undocumented remainder is left to the schema.

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 two-verb workflow (draft RFP, then evaluate bids) with the exact artifacts and scoring basis (buyer-approved rubric, hard disqualifiers). It also names the underlying stage tools (xrfp-drafter, xscore-bid-evaluation), so an agent can distinguish this bundled recipe from the standalone siblings without opening the schema.

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?

'Fixed sequence: rfp → evaluation' plus 'Drafted requirements remain provisional' tells the agent this is a coupled two-stage run, not a menu. There is still no explicit statement of when to prefer this over calling xrfp-drafter or xscore-bid-evaluation on their own, so it stops short of naming alternatives/exclusions.

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