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 that approval requirements are org-configurable and business workflow approvals always apply, which is useful operational context, but it omits pagination behavior and ordering despite the offset/limit params.

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?

It is short and front-loads the usage trigger, but the opening clause is filler and the approval sentence is somewhat boilerplate that repeats organizational policy rather than tool behavior. Most of the sentence budget is spent on context rather than mechanics.

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 needn't be explained, and the read-only annotations cover safety. Still, with all four params undocumented and no guidance on choosing among the several invoice-listing siblings, an agent lacks enough to call this confidently.

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% and none of the four params are documented in the schema. The description only implies that vendorId is required ("for a vendor") and says nothing about limit, offset, or search, leaving three params unexplained.

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?

"Read invoices for a vendor" gives a clear verb and scoped resource, so an agent knows it's a vendor-scoped invoice listing. However, it does not distinguish itself from close siblings like list_invoices, list_site_invoices, and list_bid_invoices, so the differentiation is left implicit.

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" implies the domain but gives no when-not guidance and never names the alternative tools (list_invoices, list_site_invoices, list_bid_invoices) that an agent must choose between. Usage is only inferable from the vendor scoping.

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