brandings

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

Annotations already declare readOnlyHint=true, etc. The description adds 'READ-ONLY' and 'Makes no changes' but does not disclose additional behavioral traits (e.g., response structure, pagination behavior beyond schema). No contradiction with annotations.

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 concise (a few lines) with front-loaded info (emoji, HTTP method). However, it redundantly repeats 'List all brandings' twice. Could be slightly more efficient but overall well-structured.

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 (list all, read-only) and full schema coverage, the description is adequate. It lacks explicit mention of pagination but parameters handle that. No output schema, but the return type is inferable.

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?

All 5 parameters have descriptions in the input schema (100% coverage). The description adds no additional meaning beyond what the schema provides, so 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 clearly states 'List all brandings' and 'List all existing branding resources,' specifying the verb (list) and resource (brandings). It implicitly distinguishes from sibling tools like 'get_branding' (singular retrieval) and 'update_branding' (modification).

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 when to use (to list all brandings) but does not explicitly state when not to use or mention alternatives. It lacks guidance like 'for a single branding, use get_branding' or context about pagination.

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