list_brands

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states it lists brands, but does not mention that it's a read-only operation (no annotation to indicate that), nor does it disclose the response format, pagination, or any side effects. For a tool with zero annotations, this is a significant gap in transparency.

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, front-loaded sentence with zero filler. It immediately states the action and scope. Perfectly concise and well-structured for its purpose.

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?

There is no output schema, so the description must explain what the tool returns. It only says 'list all brands' without specifying the return format (e.g., brand IDs, names, objects). Additionally, it doesn't clarify if 'access' implies authentication context or any prerequisites. For a tool with no annotations and no output schema, this is incomplete.

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 is empty with 100% coverage (trivially). Per the rubric, 0 params earns a baseline of 4. The description adds no parameter-specific meaning, but that's not needed when there are no parameters to describe.

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 states a specific verb ('list') and resource ('brands') with an explicit scope ('you have access to'). It clearly distinguishes from sibling tools like list_indexes or list_topics by naming the exact entity. However, it doesn't explicitly differentiate from other brand-related tools (e.g., create_brand, scan_brand), so it's slightly below a 5 for not noting any alternative.

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 gives clear context: it's for retrieving accessible brands. But there is no explicit guidance on when to use this tool versus alternatives, nor any mention of when not to use it. For a trivial list operation, the implied usage is obvious, but the lack of any exclusion or alternative reference keeps it at a 'clear context, no exclusions' level.

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