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

Annotations already declare the safe, idempotent, closed-world read profile, so the bar is lower. The description does add genuinely useful context beyond them by naming the returned metrics (award count, largest award, stock move) and the billing cost of 1 credit with a 25 calls/day free-tier cap. It leaves the key behavioral question unanswered: what time period 'the window' actually covers.

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?

A single dense sentence that front-loads what the tool returns and appends cost information, with essentially no wasted words. The phrase 'in the window' is undefined filler that costs clarity without adding 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 only two optional parameters and no output schema, the description carries the burden of explaining return values, and it does so by enumerating the metrics returned. The main gap is the undefined time window, which determines what the ranking actually means 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 coverage is 100%, so both parameters (sort enum and limit range) are already fully documented and the description need not repeat them. It does add meaning for the default sort by explaining that rankings are relative to market cap, which ties to pct_of_market_cap, but it adds nothing for limit or the 'total' alternative.

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 names a specific resource (public companies) and a specific ranking basis (total federal awards relative to market cap) plus the returned fields, so the tool's purpose is unambiguous. It does not, however, distinguish itself from siblings such as contract_shocks or federal_contracts, so an agent must infer the boundary from names alone.

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 mention of when this ranked view is preferable to the per-company contract tools, no exclusions, and no prerequisites. The only operational guidance is the credit cost, which is a budgeting note rather than alternative selection.

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