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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing that resolution is single-item ('one exact') and that the returned identity is 'minimized' (a reduced projection, not a full record). It does not cover error behavior for unresolvable IDs or any rate limits.

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 sentence with no filler, front-loading the action and resource before the input/output qualifiers. Every clause 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?

With no output schema present, the description must carry the return-value burden, and 'minimized federal award identity' only gestures at the shape without naming fields or indicating what 'minimized' excludes. The input side is fully covered, so the definition is adequate but leaves a real gap on output expectations.

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 description coverage is 100%, so the single parameter and its rejection of free text are fully documented in the schema. The description restates the accepted identifier types but adds no syntax, format, or validation detail beyond what the schema already provides. Baseline 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 ('Resolve'), a precise resource (federal award identity), and the exact input class (USAspending generated award ID or PIID) along with the narrowed output ('minimized federal award identity'). An agent can distinguish this lookup from the sibling analysis tools (analyze_recompete_signal, build_contract_lifecycle), though no sibling is named 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?

The phrase 'one exact ... ID' implies this is a strict, single-identifier resolution step rather than a search or batch operation, which is useful usage framing. However, there is no explicit statement of when to use this versus the siblings, and no prerequisites or failure conditions are described.

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