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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds genuine behavioral value by disclosing what the response contains (status, line items, totals, memo, and links to the resulting invoice or subscription), which tells the agent about the data shape after the read.

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 tightly packed sentence front-loads the operation and the identifier, then lists the returned fields, followed by the endpoint. No sentence is wasted and nothing needing emphasis is buried.

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 helpfully enumerates the returned fields, which is the main thing an agent would otherwise lack. For a single-parameter read tool with readOnlyHint and full schema coverage, this is nearly complete; only an explicit pointer to list_quotes for browsing is missing.

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 100% and the single parameter carries its own description ('The quote_id (a number)'), so the schema does the heavy lifting. The description's 'by quote_id' merely restates the parameter without adding format or constraint detail, making the baseline 3 appropriate.

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 ('Get one quote by quote_id') and enumerates the returned content (status, line items, totals, memo, links), which cleanly distinguishes it from the sibling list_quotes and create_quote. An agent can identify the operation and its scope without opening any schema.

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?

The phrase 'by quote_id' implies the retrieval condition and the GET endpoint confirms a read by identifier, but there is no explicit when-to-use or when-not-to-use statement and no named alternative such as list_quotes for browsing. Usage is implied rather than guided.

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