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

Annotations already declare the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), so the description's job is to add context. It usefully scopes the write to the brand record only, clarifying that related entities are not created, but says nothing about duplicate handling (relevant given idempotentHint=false), permissions, or failure modes.

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 short sentences, trigger first, scope boundary second, zero filler. Nothing could be removed without losing information.

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?

An output schema exists so return values need not be explained, and the annotations cover safety. What remains thin is the single undocumented parameter and the absence of any statement about duplicate-name behavior or what the newly created brand contains.

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?

The single 'name' parameter has 0% schema description coverage, and the description says nothing about it. The schema's minLength/maxLength constraints and the fact that name is required are the only guidance; the description adds no meaning about what a valid brand name is.

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 and resource ('Create a brand') and implicitly separates itself from the save_* siblings by listing what it does not add (claims, offers, proof, voice, banned phrases). It does not name those siblings outright, so an agent must infer the routing, but the boundary is legible.

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?

Gives one trigger condition ('when the user asks for one') but names no alternatives and states no prerequisites or exclusions. The negative list hints at where other data belongs, but the agent is left to work out which tool to call for claims/offers/voice.

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