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

The readOnlyHint annotation already signals a safe read operation. The description adds useful scoping context ('workspace's brands') and explains the output's purpose, but it does not disclose additional runtime behavior such as pagination or absence of filtering. The schema covers cursor mechanics, so the description carries no contradiction and adequate but minimal behavioral context.

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 two sentences with no filler. The first sentence names the operation and scope; the second provides concise domain context that helps the agent understand why the result matters. It is front-loaded and 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 optional-paginated list operation with a read-only annotation, the description explains the resource, the return value's role, and the workspace scope. The schema handles cursor behavior, so the description is nearly complete; it only stops short of explicitly noting that full brand objects, not just IDs, are returned.

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 single cursor parameter has 100% schema description coverage, including strong guidance about the opaque token and when to omit it. The description itself does not add parameter-level details, which is acceptable since the schema already carries the full semantic burden.

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 identifies the operation ('List') and the resource ('the workspace's brands'), and adds a concrete definition of what a brand is and how the result relates to template brand references. It does not explicitly contrast with sibling operations like get_brand, but the verb-and-resource pairing is unambiguous.

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 a concrete use case: retrieving the brand IDs that a template's brand reference points at. It does not spell out exclusions or explicitly name alternatives, but the context is clear enough to guide an agent's choice between listing and other brand operations.

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