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 real value by disclosing the return scope (the quote plus any work already approved from it), which matters because there is no output schema. It still says nothing about missing/expired quotes, permissions, or error behavior.

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 short sentence, front-loaded with the verb and resource, with no filler. The brevity is efficient, though it borders on under-specification given the tool's role in a large capacity family.

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 single-parameter read with no output schema, the description should at least anchor the identifier and clarify the mismatch with the "Reopen a quote" title. Neither is addressed, so an agent cannot confidently distinguish this from other capacity read tools.

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 0% for the single required quote_id, so the schema supplies only a type and minLength. The description does not compensate with any hint about the identifier's format or where to obtain one, leaving the only parameter semantically thin.

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 gives a specific verb ("Reads") and resource ("quote") and adds that it returns approved work derived from the quote. However, it never explains what a capacity quote is or how it differs from adjacent siblings such as get_capacity_request, get_capacity_balance, or quote_capacity_work, and the title "Reopen a quote" points at a different concept than the read-only description.

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 guidance on when to call this versus the other capacity-family getters, and no preconditions such as where a quote_id comes from or what states a quote can be read in. The agent must infer usage entirely from the name.

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