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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description needs to add non-obvious behavior. It does: secret deliverables are decrypted only for the buyer and redacted for everyone else. This is valuable, non-obvious behavioral context that helps an agent reason about response contents and permissions.

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?

Two concise sentences with no fluff. The core fetching action is front-loaded, followed by access scope and the important redaction behavior. Every sentence earns its place.

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?

For a simple single-parameter read-only tool with no output schema, the description covers the resource, the deliverable contents, access sides, and the critical redaction rule. It is nearly complete, though it could have explicitly named the sibling list tool as the alternative when the user needs multiple quotes.

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%: the only parameter, service_quote_id, is already documented as 'UUID of the quote thread to fetch.' The description adds no additional parameter-level detail, so it relies on the schema as expected.

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 states a specific verb ('Fetch'), a specific resource ('one service quote thread'), and what it includes ('its deliverables'). It also clarifies access scope ('Buyer or seller side'), which distinguishes it from list-style siblings like services_list_my_quotes.

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 description implies when to use it (fetch a single quote thread with deliverables) and mentions both buyer and seller sides, but it does not explicitly contrast with alternatives like services_list_my_quotes or services_get_listing. Usage context is present but no exclusions or alternative routing are given.

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