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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds the useful behavioral detail that invoices and quotes are returned as separate lists and that the quote-to-invoice conversion is included, but says nothing about scope (all records vs. filtered), volume, ordering, 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 that packs the resource list, the invoice state fields, and the conversion linkage with no filler. The nested parenthetical is slightly dense but every clause carries information.

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 carries the burden of explaining return content, and it does list the key invoice fields and the separate quote list. It leaves open how large the result is, whether it spans all time or a default window, and whether customer or project identifiers accompany each record, which matters for a broad context tool.

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 tool takes zero parameters, so there is no parameter meaning to add; the baseline for a no-parameter tool is 4. The description correctly implies no filtering input is required, since it describes an unfiltered dump of the user's invoices and quotes.

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 names the two resources returned (invoices and quotes) and the specific fields carried with invoices: payment state, due date, overdue status, reminder level, plus the quote-to-invoice conversion link. That is concrete enough to distinguish it from a single-resource tool like listQuotes or fetchQuoteDetailContext, though it never states the operation verb (fetch/list) and relies on the name for that.

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 or when-not-to-use guidance and no named alternative. With siblings such as fetchIncomingInvoicesContext, fetchOverdueIncomingInvoices, listQuotes, and fetchQuoteDetailContext present, an agent gets no signal about why it would pick this combined overview over those narrower tools.

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