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

Annotations already declare the full safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the behavior contract is covered. The description adds the returned field set, which is genuinely useful given there is no output schema, but it does not disclose anything beyond payload contents (no error behavior for a missing group, no auth notes).

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?

Two sentences, front-loaded with the action and immediately followed by the concrete contents of the response. No filler; the only mild redundancy is the restated 'Get brand instructions' header.

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 single-param read tool whose annotations cover the safety profile and which has no output schema, the description compensates well by enumerating the returned fields. It is only missing the disambiguation from sibling getters and any failure-mode context, which keeps it short of a 5.

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?

There is a single parameter with 100% schema description coverage; the schema already documents groupId as the content group UUID with a pattern constraint. The description adds no syntax or format meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb ('Get') and resource ('brand instructions'), and expands it with the exact payload fields (brand profile, generation settings, tone, auto-generation flags, YOLO mode). The purpose is unambiguous on its own, but it never distinguishes itself from similarly named siblings like getBrandContext or getContentGroup, so an agent cannot route confidently between 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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as getBrandContext or getContentGroup. The agent is left to infer from the name alone when this tool is the right choice.

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