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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the result cap (5), the ordering, the reduction to 3 records on the free tier, the ~3 calls/visitor/24h rate limit, and the auth mechanism (GlobalGov sign-in or X-API-Key) that lifts it. These are exactly the operational traits an agent needs to set expectations and handle throttling.

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?

Front-loaded with scope, matching rule, and ordering before the tier details. Slight waste in promotional phrasing ('Fast, index-backed lookup', 'a taste of'), but the free-tier paragraph carries genuine decision-relevant information.

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 no output schema, the description does the necessary work of describing the return shape (up to 5, deadline-ordered) and the degradation path. It does not cover what happens on an invalid or stale slug or when zero matches exist, which is the main remaining gap for a lookup tool.

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?

There is a single parameter and schema coverage is 100%, with the schema already explaining that the slug comes from a previous result. The description reinforces 'given record slug' but adds no format, derivation, or error semantics beyond 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?

States a specific verb and resource ('Up to 5 open solicitations related to a given record slug') and goes further by naming the matching logic (country + NAICS code) and ordering (nearest deadline). This clearly separates it from search_solicitations (query-driven) and get_solicitation (single fetch by slug).

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?

The phrase "Useful for 'what else is open like this?'" gives a concrete usage context, and it implies the prerequisite of having a slug from a previous result. It does not explicitly name alternatives such as search_solicitations for direct NAICS filtering, so routing is implied rather than spelled out.

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