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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely non-obvious context: no contact details are returned, and award records may be incomplete so the agent should caveat results. It stops short of describing pagination or truncation of the top NAICS/agency lists.

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-loads the when-to-use condition and keeps the exclusion last, which is good ordering. It is slightly long because it enumerates returned fields and adds a presentation instruction ('Print each recent award's url and source_url as markdown links'), but each sentence carries actionable content.

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 an output schema present, the description does not need to enumerate return values, yet it still lists them usefully and covers the main risk (incomplete records) plus the UEI provenance. Nothing critical for correct invocation is missing, although the return list is partly redundant with the output schema.

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% and the schema already supplies the pattern and the exact same example ('C3KXNLTAAY98'). The description's only addition is provenance ('e.g. from a search_awards row'), which is mildly useful but does not go beyond the schema in any substantive way, so the baseline of 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 ('one firm's government award history') and explicitly scopes it to when the UEI is known. It distinguishes itself from search_awards by naming the alternative for name/NAICS lookup, so an agent can route without opening either schema.

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?

Gives an explicit trigger ('when the user wants one firm's ... and its UEI is known, e.g. from a search_awards row') plus explicit exclusions ('Do not use for finding firms by name or NAICS (search_awards) or for contact details'). Both the when and the when-not are named with their alternatives.

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