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

With no annotations, the description carries the burden. It transparently names the data source (SAM.gov), the data fields, and a clear limitation (no price forecast). It does not mention potential caveats like data freshness or that sector/agency 'hunting' is not filterable via parameters, but for a read-only list, the transparency is solid.

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?

Three sentences, each purposeful: the first defines the tool's output, the second gives usage triggers, the third states a limitation and redirects. No fluff, well front-loaded.

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 simple one-parameter list tool, the description covers the essential context: what is returned, when to use, and a key limitation. However, it could more explicitly differentiate from sibling tools like 'upcoming_recompetes' and clarify that sector/agency filtering isn't a direct parameter. Still, it is more than adequate.

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?

The input schema already fully documents the only parameter (limit) with bounds and default. The description goes further with usage guidance ('Use 5 to 10 for an exploratory question, and the ceiling only when the user asked for the full list'), which adds real value beyond the schema.

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 solicitations currently open, sourced from SAM.gov, with specific fields (agency, NAICS, place of performance). It distinguishes itself from siblings by emphasizing 'OPEN right now' and the bidding context.

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 tells when to call this tool: when the user asks what is open, hunts for opportunities in a sector/agency, or wants to know what they can bid on. It also provides an explicit alternative for price forecasts by pointing to an external URL, which counts as a when-not-to-use.

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