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

No annotations are provided, so the description carries the full behavioral burden, yet it only discloses the paywall gating ("paid plans") and the returned fields. It says nothing about read-only semantics, pagination/result limits (size maxes at 100), whether defaults are applied when no filters are passed, or how results are ordered by default.

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?

It is a single compact statement with the core idea (recompete radar) front-loaded, followed by a useful enumeration of what comes back. The field list is slightly redundant with the parameter names but compensates for the absent output schema.

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 12-parameter, all-optional tool with no output schema and no annotations, the description does cover access gating and return fields. However, it omits what happens with zero filters (implicit 6-to-18-month default window), result ordering defaults, and how it relates to sibling SAM tools, leaving real gaps for an agent deciding whether to call it.

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 twelve parameters are already fully documented at the field level and the baseline is 3. The description adds marginal value by naming the return attributes (value, agency, NAICS, set-aside, offers received, linked notices), but it never explains the filters (size, sort, endFrom/endTo, hasNotice) or their interaction.

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 phrase "Recompete radar: federal contracts ending soon with the incumbent" conveys the resource being surfaced, but it is a noun fragment with no verb, so it is ambiguous whether the tool searches, lists, or analyzes. There is no differentiation from nearby siblings like sam_opportunities, sam_opportunity, or federal_awards, which an agent could easily confuse with this one.

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 guidance on when to use this versus sam_opportunities or federal_awards, and no exclusions or prerequisites beyond the cryptic "(paid plans)" tag. The agent must infer that this is the "contracts expiring soon" variant from the field list alone.

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