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

With no annotations, the description carries the full burden of disclosure. It adds value by stating the required Bearer authentication and the specific output fields (product counts and slugs). However, it does not mention potential pitfalls like pagination, rate limits, or exact response structure, which would be useful for a production consumer.

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 stating exactly what the tool does, followed by a crucial authentication requirement. There is no wasted verbiage; 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?

For a simple list tool with no parameters, the description is complete: it states the resource, the included fields, and the auth requirement. Although there is no output schema, the description's mention of 'product counts and slugs' sufficiently conveys the expected return structure.

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, so the baseline is 4. The description adds no parameter-level information, but none is needed since the input schema is empty. The schema coverage is effectively 100%, and the description is not expected to elaborate on nonexistent parameters.

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 the specific verb 'Return' with the resource 'brands' and specifies the output includes 'product counts and slugs.' This clearly distinguishes it from sibling tools like list_products or list_orders, which operate on different entities.

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 clearly indicates this tool is for retrieving all brands, and the context of 'every brand' implies use when a complete list is needed. While it doesn't explicitly exclude alternatives, the sibling tools are all for different resources, making the usage context unambiguous.

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