ghl_brand_board_get_voice

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful operational context beyond annotations, including the exact endpoint, version header, token requirement, and OAuth scope, though it does not describe the response payload.

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 compact and front-loads the core retrieval action and endpoint. There is minor redundancy between 'Get Brand Voice' and 'Get a brand voice by ID', and the source metadata is more internal than agent-useful, but it remains efficient.

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 read-only retrieval with two required, fully documented parameters, the description covers the endpoint, auth token requirement, and OAuth scope. It lacks return-value context, but no output schema is provided and annotations already cover the safety profile.

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 description coverage is 100%, so both parameters are already documented in the input schema. The description says 'by ID' but adds no syntax, format, or validation details beyond what the schema provides, making the baseline 3 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 states a specific verb and resource: 'Get a brand voice by ID', and includes the concrete endpoint. It clearly identifies retrieval by ID, but does not explicitly distinguish this tool from siblings like ghl_brand_board_list_voices or ghl_brand_board_get_by_id.

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 prerequisites such as requiring a Sub-Account token and OAuth scope, but provides no guidance on when to use this tool versus alternatives. It does not mention list/create/update/delete voice siblings or conditions for selecting this retrieval tool.

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