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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds an approval caveat (org-configurable MCP approvals plus business workflow approvals), which is real context beyond the annotations, but it is boilerplate that does not say whether any approval applies to a pure read, nor does it mention pagination behavior given limit/offset.

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 with the functional statement placed second rather than first. The opening and closing sentences are organizational boilerplate that would not be missed if removed.

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 not be described, and the read-only nature is fully covered by annotations. The remaining gap is that four parameters at 0% schema coverage go unmentioned, and no guidance distinguishes this from other invoice list 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 0%, so the description must carry parameter meaning, yet it never names bidId, limit, offset, or search. Only the phrase "for a bid" hints that a bid identifier is required; the pagination and search parameters are entirely undocumented in both schema and description.

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 sentence "Read invoices for a bid" gives a specific verb and a scoped resource, so an agent knows it lists invoices tied to a single bid. It does not distinguish itself from the many other invoice-listing siblings (list_invoices, list_site_invoices, list_vendor_invoices), leaving the bid-scoping scope as the only differentiator inferred rather than stated.

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 invoices records in the connected organization" is generic framing rather than a selection rule, and it never says when to prefer this over list_invoices or list_site_invoices. No exclusions, prerequisites, or alternative routing are provided.

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