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

Beyond the readOnlyHint annotation, the description flags two important behaviors: list and get may return different fields, and quote references are not unique. This helps the agent avoid misinterpreting representation differences as failures and makes the id-based lookup advice actionable.

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?

The description is compact and front-loaded with a crisp one-sentence statement of purpose, followed by two high-value caveats. Every sentence contributes useful context with no filler.

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?

The description captures the most surprising API behavior and makes the callable first steps clear, but it does not describe the returned fields, pagination defaults, or how results are structured. Given that there is no output schema, this leaves some important context unresolved for an agent that must interpret results.

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?

With only 50% schema coverage, the description should compensate for undocumented parameters like top, page, skip, filter, orderBy, and pageSize, but it does not mention them. The quote-reference comment relates to data semantics rather than parameter meaning.

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 opens with 'Lists BRC quotes', a specific verb and resource that immediately identifies the operation. It also distinguishes list behavior from get behavior via the field-mismatch warning, though it does not explicitly differentiate this from the similar brc_list_customer_quotes sibling.

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 about when to prefer this tool over brc_list_customer_quotes or brc_get_quote, and no mention of scenarios that call for pagination. The list-vs-get caveat is useful but is more about interpretation than decision-making about which tool to invoke.

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