brand_list

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

Without annotations, the description carries the full burden. It discloses that the output is a list grouped by category and mentions the supported count. However, it does not describe behavior like sorting, pagination, or the exact structure of the grouping beyond 'grouped by category'. Adequate but not rich.

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 sentence with no filler words. It conveys the action, scope, and organization in 8 words. Every word earns its place.

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 (one optional parameter, no output schema), the description covers the essential purpose. However, it omits details about the output structure (e.g., whether it's a list of objects with brand name, category, etc.) and any potential limits. Adequate for a minimal tool but could be more explicit.

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% (the category parameter is documented with enum values in the schema). The description adds no additional meaning beyond restating 'Optional category filter' and listing the options, which are already in the schema. Baseline 3 is appropriate.

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 uses a specific verb ('List'), identifies the resource ('brands'), and adds a distinguishing detail ('grouped by category') while noting the exact count (328+). This clearly differentiates it from sibling tools like brand_fetch_design_md, which fetch designs for specific brands.

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 implies usage for obtaining a list of brands grouped by category but does not explicitly state when to use it vs. alternatives or when not to. Since no sibling tool serves exactly the same purpose, the context is clear but lacks explicit guidance.

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