ghl_brand_board_list_voices

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

Annotations already declare readOnlyHint=true, destructiveHint=false, etc., covering safety. Description adds endpoint and pagination details but no extra behavioral traits (e.g., rate limits, auth, or data freshness). OpenWorldHint is not explained.

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?

Three short sentences covering title, action, endpoint, and pagination. However, the first line repeats the title already available. Could be tightened slightly, but overall efficient and front-loaded.

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 no output schema, the description explains how to retrieve all results via pagination. Missing details like default sorting or response structure, but annotations and schema compensate. Mostly complete for a list operation.

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?

Schema coverage is 100% with each parameter described. Description adds context that limit/offset are used for pagination, but does not enhance meaning beyond schema. For full schema coverage, 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?

Title 'List Brand Voices' and description 'Get list of brand voices for a location' clearly state the verb (list/get) and resource (brand voices scoped by location). Distinguishes from sibling tools like ghl_brand_board_get_voice (single) and ghl_brand_board_create_voice (create).

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?

Description mentions pagination with limit/offset but does not explicitly state when to use this tool vs alternatives (e.g., get_voice for a specific voice). No direct guidance on when not to use or preference over siblings. Agent must infer from tool names.

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