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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond them: the data source (FPDS) and the page size ('ten at a time'). It stops short of explaining how to advance pages or what a result record contains, which is a meaningful gap for a paginated search.

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 the resource and then lists filters, with zero redundant phrasing. The 'Plumbline:' vendor prefix is minor overhead but everything else earns its place.

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 read-only, annotation-covered search tool with no output schema, the description covers the data domain, source system, filterable fields, and page size, which is enough for an agent to invoke it correctly. Remaining gaps are pagination mechanics and result shape, which are secondary given the annotations already establish the operation is a safe, repeatable read.

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?

With 0% schema description coverage, the description must carry the semantic burden, and it does explain four of the five parameters by mapping them to vendor name (recipient), NAICS code, place-of-performance state, and fiscal year. The 'start' offset parameter is never explained, and the description gives no format hints (e.g. two-letter state, six-digit NAICS) beyond what maxLength constraints already imply.

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 (US federal contract actions, including awards and modifications) and enumerates the filter dimensions: vendor name, NAICS code, place-of-performance state, and fiscal year. The verb 'search' appears only in the title and is implied here by the filter list, but an agent can still tell exactly what data domain this covers. Siblings like entity_lookup and screen_sanctions are clearly different domains, so no differentiation is needed.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives are named. The filter list implies the kind of lookup this suits, but an agent receives no help deciding between this and other lookup tools, nor any prerequisites or example queries.

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