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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds real context beyond them: the guarantee of 'No generation or charge' and the pagination contract (nextCursor bound to the same kind). It stops short of noting rate limits or result-size caveats.

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?

Three dense sentences, front-loaded with what is returned, followed by the pricing disambiguation and the pagination rule. No filler, though the enumerated payload list is long enough to border on schema duplication.

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?

With an output schema present, return-value explanation is optional, and the description still supplies the key contract points (pagination binding, no charge, prices vs quotes). Nothing essential to correct invocation is missing for this read-only browse tool.

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 kind, limit, and cursor are fully documented in the schema. The description's pagination note ('nextCursor with the same kind') largely restates the cursor field description rather than adding new meaning, so the baseline 3 applies.

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 ('Returns the current Brix36 model catalogue') and enumerates the payload contents (profiles, settings, media limits, availability reasons, prices). It also separates itself conceptually from pricing-quote siblings by noting starting prices are distinct from generation quotes, though it never names a sibling tool.

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 line 'Starting prices are distinct from generation quotes' implicitly routes the agent to the quote tools for actual pricing, and 'No generation or charge' implies this is a pre-flight browse. However, there is no explicit when-to-use or when-not-to-use statement or named alternative, leaving usage inferred.

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