brc_list_quotes

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

Without annotations, the description must disclose behavioral traits. It does not mention whether the operation is read-only, if pagination is involved, or any side effects. The description is silent on key behaviors.

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 extremely short, but conciseness is not a virtue when it omits essential information. It does not earn its place as it provides no value beyond the tool name.

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?

Given the complexity of 7 parameters and no output schema or annotations, the description is severely incomplete. It fails to explain how the parameters control the listing, what the response contains, or any constraints.

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 43%, but the description adds no parameter information. It does not explain how to use the parameters (e.g., pagination controls, filtering) beyond what the schema already provides. For low coverage, the description should compensate, which it does not.

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 'Lists BRC quotes' merely restates the tool name without specifying the type of quotes or distinguishing it from similar siblings like brc_list_customer_quotes or brc_get_quote. It provides no verb beyond 'lists' but fails to clarify scope or context.

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?

No usage guidelines are provided. The description does not indicate when to use this tool over alternatives, such as when listing all quotes vs. customer-specific quotes, and omits any prerequisites or context.

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