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

Goes well beyond the destructiveHint annotation by describing exactly what mutates (slides get background/typefaces/text colors, interface brand.css is rewritten) and what is preserved ('sizes are kept'), plus the downstream effect on var(--brand-*) styling. This is substantial disclosure of mutation semantics for a destructive tool.

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-loads the core action, then spends each following clause on one parameter's distinct effect with no filler. Dense but every sentence carries actionable detail.

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 destructive mutation tool with no output schema, the description covers effects and verification well. It does not, however, clarify that at least one of deck/interface/kitId must be supplied (all params are optional), leaving an ambiguity an agent could trip on.

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 100%, so the schema already documents all five parameters (baseline 3). The description adds real value beyond it by explaining accent's runtime meaning and kitId's default-to-workspace-brand behavior, though it says nothing extra about workspace or interface beyond the schema text.

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 ('Restyles a piece in the brand') and enumerates the distinct effect per target type (deck, interface, accent, docs). This lets an agent distinguish it from siblings like napkin_deck_set_theme or napkin_brand_get without opening schemas.

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 clear conditional guidance for the accent parameter ('use it when the piece is about one product or campaign that has its own color') and explicitly says docs need nothing. It also routes verification to napkin_slide_view, but does not name alternative tools for setting deck styling, so no explicit when-not guidance against siblings.

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