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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds one genuinely new behavioral fact — the pay link is conditional ('when one is ready') — but says nothing about auth scope, not-found behavior, or pagination.

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?

One front-loaded sentence with no filler; the payload contents are stated immediately. 'Open' is a slightly loose verb for a read-only retrieval, but nothing is wasted.

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 description must describe returns and it does so partially (line items, conditional pay link). For a low-complexity one-parameter read whose annotations cover safety, this is adequate, but the identifier format and error/not-found behavior remain unaddressed.

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?

The single invoiceId parameter has 0% schema description coverage, so the description carries the burden and does not meet it: it never states the identifier's format, source, or whether it accepts the invoice number vs an internal ID. 'Open one invoice' only restates that an identifier is needed.

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 and resource ('Open one invoice') and enumerates the payload ('line items and the pay link'), which separates it from the list_* siblings that return collections. It does not name an alternative, but the singular scope is unambiguous.

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?

There is no when-to-use statement, no prerequisite (e.g. where invoiceId comes from), and no routing away from list_overdue_invoices/list_recent_invoices/list_unpaid_invoices or find_estimates. Usage is only weakly implied by 'one invoice'.

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