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

Annotations declare readOnlyHint=true, yet the description describes storing user-supplied data ('Save a font... optional logoBase64'), which is a persistent write. An agent reading both gets conflicting signals about whether the call mutates state. The title annotation ('Prepare client burn') also does not match the described behavior, compounding the confusion.

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?

Everything is packed into two sentences with no filler — the allowed-values list and the follow-up call are both actionable. The opening is field-enumeration rather than a scope statement, so it is dense but slightly back-loaded on the 'what am I creating' question.

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?

With no output schema, the description should say what comes back; it only implies a brandPresetId exists by telling the caller to pass it onward. The required `name` field and any overwrite/idempotency behavior (what happens when saving a preset with an existing name) are absent, which matters for a tool whose annotations are already unreliable.

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 coverage is 0%, so the description has to carry the load, and it does well: it lists the permitted font family values, the #RRGGBB color format, the three position values, and the accepted image encodings for logoBase64. The one gap is the required `name` parameter, which is never mentioned anywhere, leaving the caller to infer it.

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 enumerates exactly what gets stored (font, #RRGGBB color, position, optional logo) and names the downstream consumers (burn_captions, preview), so an agent knows the resource being created. It never states the noun directly — 'Save brand preset' is only implied by the name/title — and it never distinguishes itself from the sibling save_custom_preset, which is the main ambiguity.

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?

'Free. Pass brandPresetId to burn_captions or preview.' gives concrete downstream usage and cost, which is real guidance. But there is no statement of when to pick this over save_custom_preset, whether a preset must exist before burn_captions, or how to inspect saved presets (list_brand_presets).

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