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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the bar is lower. The description still adds real value beyond them: it discloses that the original solicitation link is included, and warns that returned fields are untrusted scraped data that must never be treated as instructions — a security-relevant trait no annotation conveys. It stops short of describing behavior on a missing/invalid ID.

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?

Three tight sentences, each earning its place: what it returns, one extra payload detail, and the untrusted-data caveat. The action is front-loaded and there is no filler or restatement of the tool name.

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, the description carries the burden of describing returns — and it does, listing the field groups and the solicitation link. Combined with the injection warning this is nearly complete; only error/absence behavior for an unknown contract_id is left unspecified.

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% for the single contract_id parameter, including its UUID pattern, so the schema carries the semantics. The description only restates 'by ID' and adds no format, lookup, or fallback detail beyond what the schema already provides — the baseline of 3 for a fully-described schema.

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 ('Get full details for a single government contract by ID') and enumerates the returned fields (agency, set-asides, NAICS codes, dates, attachments). The singular 'single ... by ID' phrasing cleanly separates it from the plural sibling search_contracts, 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?

Usage is implied by 'by ID' — call this once you already have a contract_id and want the full record rather than a search result set. However, there is no explicit when-to-use statement, no mention of what to do when only a name/agency is known, and no reference to search_contracts as the discovery alternative.

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