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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive). The description adds genuinely useful context beyond them: that dates are estimates from recorded periods of performance, that results are explicitly not a prediction of a solicitation, and a concrete billing/rate model (one accepted call = one use; up to 30 free follow-ups within 30 minutes). It does not contradict the annotations.

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 billing and estimate caveats earn their place, but the purpose sentence is buried behind three disclaimers, two of which are redundant ('Not affiliated with the U.S. government, GSA, or SAM.gov' and 'Not a U.S. government service'). Front-loading the actual capability would make it far more scannable.

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 read-only annotations and no output schema, the description adequately conveys what the data is (estimated recompete candidates) and the cost model, but omits return shape and any differentiation from the recompete siblings. Minimum viable for a 2-param read tool, with clear gaps.

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 50%: 'naics' is documented in the schema while 'limit' is bare. The description mentions no parameters at all, so it fails to compensate for the gap — no guidance on NAICS code format, what a limit of 25 means in practice, or default behavior.

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 clear verb+resource: 'Find contracts nearing end of performance and likely recompete candidates.' An agent can tell the general intent. However, it never distinguishes itself from near-identical siblings like find_likely_recompetes, get_recompete_calendar, and get_recompete_detail, so routing between them is left to guesswork.

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?

There is no when-to-use guidance, no prerequisites, and no named alternative. The billing hint ('Follow-ups within 30 minutes after a search ride free') implies this is a search-style call with follow-ups, but it never says when to pick this tool over the many recompete siblings.

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