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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. Beyond that the description adds real behavioral context by enumerating the returned fields, including the noteworthy conditional that invoice_id is present only "if any" (i.e. only after conversion). It does not cover error behavior for an unknown id or auth requirements.

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 tight clauses, front-loaded with the action and its id argument before the payoff of what comes back. The appended "GET /api/v1/quotes/{id}" anchors it to a concrete endpoint with no wasted words.

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?

There is no output schema, so the description must (and does) characterize the return payload — line items, totals, status, and the conversion link. Combined with a fully documented single parameter and readOnlyHint, an agent has everything needed to call it correctly.

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 single parameter has 100% schema description coverage, including the hashed-id format example, so the schema does the heavy lifting and baseline 3 applies. "By id" in the description merely restates the schema and adds no syntax or format detail beyond it.

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 and resource ("Fetch one quote by id") and enumerates the payload (line items, totals, status, converted invoice_id), so an agent can distinguish it from bulk siblings like invoiceninja_list_quotes. It stops short of naming any sibling explicitly, and the get_invoice/convert_quote_to_invoice overlap is left to inference.

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 implied by the shape of the tool — you call it when you have a quote id and need the detail record — but there is no explicit when-to-use, no when-not-to-use, and no pointer to invoiceninja_list_quotes for enumeration or invoiceninja_convert_quote_to_invoice for the conversion action. Adequate, not guiding.

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