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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered structurally. The description adds the underlying endpoint (GET /api/v1/quotes), which is mildly useful context, but says nothing about pagination behavior, default page size, or what a result set contains. Adequate given the lower bar set by annotations.

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 short sentences with the purpose front-loaded and the endpoint detail trailing; nothing is wasted or 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?

For a read-only list tool with fully documented inputs and no output schema, the definition covers purpose, filterability, and the API mapping. It does not describe the returned record shape or pagination envelope, a minor gap since no output schema exists to fill it.

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%, so every parameter already carries its own semantics (sort syntax, per_page range, status values, hashed client id). The description only restates that client and status filtering exist, adding no syntax or format detail beyond the schema. Baseline 3 is correct.

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 ('List quotes') and disambiguates terminology with '(estimates)', which matters in Invoice Ninja where estimates and quotes are the same entity. It does not explicitly contrast itself with siblings like invoiceninja_get_quote or invoiceninja_list_invoices, but the resource is unambiguous.

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 notes it is 'filterable by client and quote status', which hints at how to narrow results, but gives no when-to-use guidance, no statement of when to prefer invoiceninja_get_quote (single record) over this list, and no prerequisites. Similar to the MID calibration example, this leaves routing to inference.

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