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

With no annotations, the description carries full disclosure responsibility. It does reveal output structure (card counts, one-line intros) and the scope (brands covered by the knowledge base), but it doesn't mention potential limitations such as ordering, filtering, pagination, or behavior if no brands exist. For a simple read-only listing tool, this is adequate but not richly transparent, hence a 3.

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 a single, well-structured sentence that front-loads the action ('List the brands') and immediately provides useful context (card counts, one-line intro, categories). Every word earns its place; there is no redundancy, filling, or unnecessary detail.

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 tool's simplicity (no parameters, no output schema), the description sufficiently covers the key elements: what is returned (brands, counts, intros) and the scope (knowledge base categories). It doesn't specify formatting, sorting, or response shape, but for a list endpoint this is a minor gap. The sibling context and the straightforward nature of the tool make the description reasonably complete, though not exhaustive.

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 tool has zero parameters, and the schema confirms this with an empty properties object. According to the rubric, 0 params merits a baseline of 4. The description adds no parameter semantics because there are none to explain, so it meets the baseline without penalty.

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 clearly states the tool's function: 'List the brands covered by this knowledge base with card counts and a one-line intro for each.' It uses a specific verb ('List'), specifies the resource ('brands'), and adds meaningful detail about the output format and categories (laser sources, cutting/welding heads, control systems). This distinguishes it from sibling tools like get_brand_overview (likely focused on a single brand) and search_parts_knowledge (search-oriented).

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 conveys clear context for use: when a user wants an overview of all covered brands, not a specific brand's details. While it doesn't explicitly name alternatives or state when-not-to-use, the sibling tool names and the list-oriented phrasing imply that this is the entry point for brand-level browsing. This meets the 'clear context, no exclusions' bar for a 4.

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