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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond that by disclaiming any approve/select/award side effect and by warning that a real UUID (not a name or partial identifier) is required, implying lookup must come from list_bids first.

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 short sentences, each doing distinct work: purpose, input constraint, and negative capability. Nothing is redundant or buried.

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?

A read-only, single-parameter getter with an output schema, so return values need no explanation. Purpose, the one input constraint, and the critical no-side-effect guarantee are all present; nothing an agent needs to invoke it correctly is missing.

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 0%, so the schema carries no prose, but the single bidId is fully constrained by format:uuid and a regex pattern. The description compensates partially by stressing the 'real UUID' requirement, which signals no fuzzy/name matching, but adds no further detail on the parameter's origin.

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 (inspect) and resource (a recorded RetailHardHat contractor bid), and enumerates what is returned: scope, amount, status, notes. This clearly separates it from list_bids (enumeration) and compare_site_bids (cross-bid comparison).

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 concrete use context ('before making a comparison') and an explicit exclusion ('Never approves, selects or awards'), which routes the agent away from decide_bid_approval_request. It does not name compare_site_bids or list_bids as alternatives, so the routing is implied rather than fully spelled out.

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