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

Annotations already cover the safety profile (destructive, idempotent), and the description adds real context: it writes exactly the passed names, mirrors the dashboard's manual fields, and warns 'never invent one.' It stops short of spelling out what an overwrite destroys, but adds meaningful behavioral guidance.

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?

Front-loaded with the action, then rationale, then the precondition. Slightly dense with parentheticals but every clause (website-sourced, dashboard parity, don't guess) 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?

No output schema, but for a mutation tool the description supplies the essential precondition workflow, the source-of-truth rationale, and cross-tool pointers. It omits success/failure behavior, which is a minor gap.

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% and each parameter (brandId, guideId, headingFont, bodyFont) is already documented, including the 'exact font name... not a guess' note. The description reinforces but adds no new parameter-level semantics beyond the schema.

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: 'Sets a brand guide's heading and body font directly.' It is readily distinguishable from sibling set_brand_logo and the broader update_brand_guide, and it clarifies it writes exact values rather than generating 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?

Gives a clear precondition ('Have the actual correct font name in hand first') and names the routes to satisfy it (ask the owner, or read from a fresh get_brand_guide result after retry_brand_ingest). It doesn't explicitly contrast against update_brand_guide, but the context is clear.

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