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

Annotations already declare the read-only, idempotent, closed-world, non-destructive profile, so the bar is lower. The description adds real content context beyond that: it discloses what the response will contain, including derived relationships (invoices created from the quote, linked project), which helps an agent decide whether one call suffices. It omits auth requirements, pagination, or behavior for a missing/invalid id.

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?

A single front-loaded sentence led by the verb and scope, then the payload contents. Every clause carries information; nothing repeats the title or the annotations.

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 one required parameter and no output schema, the description usefully enumerates the return contents and the cross-entity relations, which is the main thing missing from structured fields. Only guidance on failure cases and sibling routing remains absent.

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 coverage is 100% and the schema itself already documents that quoteId accepts either a database id or the human-readable document number. The description only echoes 'by quoteId' and adds no format, validation, or lookup-fallback nuance.

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+resource: 'Full details of one quote or invoice by quoteId', and enumerates the payload (positions, totals, customer, linked invoices, project). That contrasts implicitly with the plural list siblings such as fetchQuotesContext and fetchIncomingInvoicesContext, but it never names a sibling or states the singular-vs-list distinction explicitly.

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?

Usage is only implied: an agent can infer it should call this when it needs the complete record for a single document rather than a list. There is no explicit when-to-use, no exclusions, and no pointer to the history, draft, or template siblings for related questions.

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