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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), but the description adds genuinely operational context beyond them: the follow-up billing window ('within 30 minutes... ride free; otherwise one accepted call counts as one use'), the affiliation-rule risk from teaming with a large business, and the caveat that size status is UNVERIFIED and must be checked in SAM.gov. This is meaningful disclosure the annotations do not carry.

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?

The text is long and front-loaded with legal disclaimers ('Not affiliated with the U.S. government, GSA, or SAM.gov. Not a U.S. government service.') rather than the tool's purpose, which appears only third. Repetitive disclaimers and a WARNING block consume space that does not help an agent decide or invoke correctly.

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 2-parameter tool with no output schema, the description conveys what kind of records come back (firms with teaming history) and the domain caveats, but it does not describe the return structure or the meaning of 'limit' beyond the schema. Adequate for invocation, incomplete on results.

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 50%: 'naics' is documented in the schema ('NAICS code for the trade lane') and the description reinforces the 'trade lane' concept, but neither the schema nor the description explains 'limit' (default 10, max 25). The description adds only marginal meaning over the structured fields, so the baseline 3 is appropriate.

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 sentence 'Find firms with a track record of teaming in a trade lane, based on historical subaward and prime-award activity' gives a specific verb+resource and the data basis. However, it is buried behind three sentences of disclaimers, and it does not distinguish this tool from the similarly named sibling 'find_teaming_partners', leaving ambiguity an agent cannot resolve from the description 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?

The description tells the agent how to present results ('information only', 'not recommendations') but never says when to use this tool versus alternatives such as find_teaming_partners or research. There is no when-to-use or when-not-to-use guidance for tool selection, only framing rules for the output.

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