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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds that revisions are 'preserved' and evidence is 'primary-source', but says nothing about pagination, result size, or how revisionsCursor behaves, which matters for a tool with a cursor parameter.

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?

Two tight sentences, front-loaded with the resource list and followed by the id-sourcing instruction. No filler; every clause carries information.

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 enumerated evidence categories usefully stand in for what gets returned, and annotations cover safety. The one gap is the unaddressed pagination cursor, which an agent would need to know about to fetch all revisions.

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 0%, so the description must compensate. It clarifies the origin and format expectation of 'id' (the exact id returned by company.awards), which is genuinely useful beyond the regex pattern, but it never mentions or explains revisionsCursor, leaving half the parameters undocumented.

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 (Read) and enumerates the exact resource set: preserved revisions, subcontractors, modifications, government-customer edges, and primary-source evidence. The line 'Use the exact id returned by company.awards' implicitly distinguishes it from the awards-list sibling, though it never names what this tool is not.

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 a clear precondition: obtain the exact id from company.awards first, which is the practical entry point for this evidence tool. It does not state when to prefer or avoid it relative to other award-adjacent siblings, so it stops short of full when/when-not guidance.

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