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

Annotations already declare readOnly/stateless/idempotent/non-destructive, and the description largely restates that, which earns no credit. It does add genuinely new behavioral context — the API key requirement and the 15-to-45,000 character input bound — that an agent cannot get from the annotations. No mention of limits on computation or handling of oversized ledgers, so not a 5.

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?

Key content is front-loaded in the first sentence, but the text is a single long run-on that recites the full tool title inside the 'use this tool when' clause — pure repetition — and packs citation lists into every sentence. Functional but bloated.

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?

An output schema exists, so the return-value enumeration is redundant rather than required, and all three parameters are documented in the schema. With auth and input-size constraints disclosed, an agent has what it needs to invoke correctly; only edge-case behavior (e.g. malformed ledgers, proposal basis validation) is unaddressed.

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 100%, so the baseline is 3. The description repeats the character range and says the two optional parameters 'calibrate the regulatory regime and threshold assumptions', adding only a slight framing gloss over the schema's own descriptions.

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: computes recoverable costs, subcontractor claims, settlement expenses and profit, and emits an SF 1435 or SF 1436 T4C settlement proposal. It enumerates the exact output sections, so an agent can distinguish this from any sibling at a glance.

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?

Explicitly names use conditions and two alternatives with their diverging purposes: scan_far_dfars_clauses for general clause flow-down audits and generate_compliance_matrix for Section L/M shall extraction. Nothing is left to inference about when to route elsewhere.

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