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

The description aligns with readOnlyHint and idempotentHint, and adds genuine behavioral context by stating the operation is review-gated and does not write to accounting systems. With annotations already covering the read-only and non-destructive profile, the added context is modest but not redundant.

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?

The description is a single compact sentence with no filler, and the core deliverable is front-loaded. It sacrifices substance for brevity, but as written it is well-structured and easy to parse.

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 13-parameter, zero-required tool with key siblings like convert_to_bid, progress_invoice, and export, this definition leaves too much implicit: source selection, approval flow, format semantics, and adapter-specific behavior are all unaddressed. The output schema and annotations provide some context, but the description alone is not sufficient for correct invocation.

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 15% across 13 parameters, and the description compensates for none of that gap. It gives no hints about how to select the source estimate, which lines or query to use, what approval or progress_pct mean, or how format affects output, leaving an agent with almost no semantic grounding for parameter choices.

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 names a deliverable ('OCE Estimator/Appraiser document or QBO handoff contract') and a verb ('Prepare'), but it never explicitly says it converts an estimate into an invoice; that is only inferable from the tool name. It also doesn't distinguish itself from the sibling estimator_estimate_convert_to_bid, so the purpose remains somewhat ambiguous.

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?

No guidance is given on when to use this tool versus estimator_estimate_convert_to_bid or estimator_estimate_progress_invoice. 'Review-gated; does not write to accounting systems' is a constraint, not a usage rule, and no alternatives or conditional selection criteria are mentioned.

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