zendesk_list_brands

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

The description discloses the output (IDs and search syntax) but lacks details on side effects, authentication needs, rate limits, or data volume. Since no annotations are present, the description could be more explicit about the read-only nature and any limitations.

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 no unnecessary words. It efficiently conveys the tool's purpose and output.

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 parameterless list tool with no output schema and no annotations, the description provides sufficient information about what the tool does and what it returns. It could be enhanced by noting that it returns all brands or any pagination behavior, but it is largely complete.

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 input schema has zero parameters, so schema description coverage is 100%. The description adds value by specifying what the output contains ('IDs and search syntax'), which indirectly helps the agent understand the tool's behavior even without parameter details.

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 'List all Zendesk brands in the account with their IDs and search syntax.' It uses a specific verb and resource, and distinguishes this tool from siblings like zendesk_search_by_brand by focusing on listing brands rather than searching within them.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The tool's simplicity implies its usage, but compared to other Zendesk tools, no direction is given on when to choose this over alternatives.

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