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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds meaningful scope-of-destruction detail beyond that: existing creatives made with the character are unaffected, which tells the agent this is not a cascading delete. It stops short of saying whether removal is reversible or what happens if the name is not found.

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 the key scope caveat. Nothing is redundant and every clause 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?

For a simple two-parameter destructive removal with full schema coverage and annotations declaring destructiveness, the description covers the essential non-obvious behavior (existing creatives unchanged). Minor gaps around irreversibility and behavior when the character is absent keep it from 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?

Schema description coverage is 100%, so both parameters are fully documented in the schema. The description reinforces the 'by name' lookup and the brand-kit context implied by 'domain', but adds no format, casing, or error semantics beyond what the schema already provides; 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?

The description gives a specific verb and resource ('Remove a registered brand character') plus the location ('from the brand kit') and lookup key ('by name'). It is clearly distinguishable from register_brand_character and get/update_brand_kit, though it does not explicitly name a sibling to contrast with.

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?

Use is implied by the inverse-of-register framing, but there is no explicit when-to-use or when-not-to-use guidance and no mention of alternatives such as editing the brand kit. An agent can infer the purpose but gets no routing advice.

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