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

With no annotations, the description carries the transparency burden. It clarifies the data nature (pre-solicitation opportunities) and notes each record includes incumbent and current contract value. However, it doesn't explicitly state whether the operation is read-only or mention return format/pagination, leaving a slight gap.

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 compact and information-dense. Four sentences cover purpose, output contents, when to call, and sibling distinction without any fluff or repetition.

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?

Given the tool's simplicity (one parameter, no output schema), the description fully covers what the tool returns, when to use it, and how it differs from a key sibling. No critical context is missing.

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% for the only parameter (limit), with the schema describing it as 'How many contracts to return, 1 to 50.' The description adds no additional parameter semantics, so the baseline of 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 clearly states the tool returns US federal contracts nearing expiry that are likely to be recompeted, before they become published solicitations. It uses a specific verb ('returns') and resource ('upcoming recompetes'), and explicitly distinguishes itself from sibling open_solicitations.

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 provides explicit when-to-use guidance: 'Call this when the user plans pipeline, asks what is coming, or wants to position ahead of competitors.' It also gives a direct comparison to open_solicitations, indicating when NOT to use it (when opportunities are already open for bids).

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