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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so safety is covered. The description adds that pagination is bounded and search is supported, plus a note that approval requirements are administrator-configurable and business workflow approvals always apply — relevant context, though the approval note is ambiguous for a read-only listing.

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?

The first two sentences say nearly the same thing ('RetailHardHat bids records' and 'List bids in your organization'), and the trailing sentence about approval configuration is generic boilerplate. The core information is front-loaded, but roughly half the text is redundant.

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?

An output schema exists, so return values need no explanation, and annotations carry the safety profile. What remains missing is guidance on the id/siteId/status filters (siteId notably requires resolving names via list_sites first, which the description does not surface) and differentiation from sibling bid tools.

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 only 33%, so the description needs to compensate but largely does not. 'Supports bounded pagination and search' merely echoes the limit/offset/search parameter names, and the id, siteId, and status filters are left entirely to partial schema text or no documentation at all.

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 states a specific verb and resource ('List bids in your organization'), which is clear and actionable. However, it does not distinguish this tool from close siblings such as get_bid_details, compare_site_bids, or list_bid_documents, so an agent must infer the boundary from names alone.

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?

'Use this when working with RetailHardHat bids records' is a restatement of scope rather than a selection rule, and no when-not conditions or alternative tools are named. There is no guidance on when to call this versus get_bid_details or compare_site_bids for bid-related questions.

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