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

With no annotations, the description carries the full burden. It usefully discloses that subsidiaries and joint ventures are rolled in and that a match explanation is returned, which is real behavioral context. But it says nothing about pagination behavior beyond the schema's size cap, whether a ticker is effectively required, or result ordering defaults.

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, tight sentence that front-loads the resource and scope. Nothing is wasted, though the same brevity is what leaves the usage and filter behavior under-explained.

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 six-parameter tool with no annotations and no output schema, the description covers the entity scoping and the subsidiary/JV rollup but not the return shape, default behavior with no ticker supplied, or how the filter parameters compose. Adequate but with clear gaps.

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 the baseline is 3; the description lifts it slightly by clarifying that the ticker parameter can also be a CIK and that matching logic is applied. It adds no detail on the filter interactions (type/agency/date) beyond what the schema already documents.

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 (retrieves) and resource (federal awards) with a clear scope: company-level, keyed by ticker, including subsidiaries and joint ventures. That scope distinguishes it from recipient-level siblings like federal_recipient/federal_recipients, though it never names them explicitly.

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?

Usage is implied by 'of a listed company by ticker' — you use it when you have a company identifier and want its awards. There is no explicit when-to-use vs. federal_awards, federal_award, or federal_recipients, and no stated prerequisites (e.g., a resolved ticker/CIK).

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