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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is well covered. The description adds useful context beyond that: it describes a patch (partial update) and states that only the active profile is mutated, with selection/creation handled outside this tool. It doesn't disclose auth, rate limits, or return behavior, so it's not a 5.

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 sentences, front-loaded with purpose, followed by usage context and a scoping constraint. No filler or repetition; every sentence earns its place.

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 output schema exists, return values need not be described. The description covers purpose, usage, and the key scope limitation. It could be more complete by clarifying that omitted fields remain untouched or by explaining the audienceSize object format, but it is otherwise sufficient for this complexity level.

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 0%, so the description must compensate. It names every updatable field conceptually (voice, themes, expertise areas, personality traits, hashtag set, audience-size estimates, bio), mapping to all seven schema properties. It does not explain the nested structure of audienceSize or field constraints, but the schema itself provides types and limits.

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 uses a specific verb ('Patch') and resource ('user's active brand profile'), then enumerates every updatable field. It also distinguishes this operation from profile selection and creation, which must happen elsewhere. An agent can immediately tell what this tool does.

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?

It explicitly states when to use it ('when the user wants Claude to refine their brand voice based on a transcript, style guide, or competitor analysis') and when not to use it ('profile selection / creation must happen in the web app'). No alternative sibling tools exist for this resource, and the boundary is clear.

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