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

Beyond the annotations (readOnly/idempotent/non-destructive/openWorld=false), it adds genuinely new context: authentication requires X-RapidAPI-Key or X-SignalTender-Key, the call is stateless, and the 15–45,000 character input bound. It restates the annotation-covered safety profile and enumerates return fields that the output schema already documents, which caps it below 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?

The core purpose is front-loaded, but the full title string 'FAR Part 48 Value Engineering Change Proposal (VECP / FAR 52.248-1) & Shared-Savings Modeler' is repeated three times and the FAR citations are restated in multiple places. Several clauses (stateless, read-only, non-destructive, output field list) duplicate structured fields rather than earning their space.

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?

With an output schema present, annotations covering safety, and 100% schema coverage, the description supplies what remains: purpose, sibling routing, auth requirements, and input size limits. Nothing an agent needs in order to invoke it correctly is missing, though the signal is diluted by repetition.

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 all three parameters are already documented in the schema, including defaults and length bounds. The description only adds that far_part_48_sharing_regime and development_and_government_implementation_costs 'calibrate the regulatory regime and threshold assumptions' — marginal value over the schema, so baseline 3 applies.

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 states a specific verb and resource: transform FinOps/AI/architecture optimizations on an active contract into a FAR 52.248-1 VECP, computing instant/concurrent/future savings and the 50%–75% contractor share. It names the exact response object and its four component sections, so an agent can distinguish it from every sibling 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?

It explicitly routes the agent away from two siblings: use scan_far_dfars_clauses for general FAR/DFARS clause flow-down audits and generate_compliance_matrix for Section L/M 'shall' extraction. The positive trigger, however, is circular ('Use this tool when executing [this tool's own title] workflows'), so the when-to-use condition is weaker than the when-not-to-use condition.

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