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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description still adds real context beyond them — the required 'demos:read' scope, that null values in the kit document are derived, and that `resolved` includes contrast warnings and feeds AI copy. No error/not-found behavior is disclosed.

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 'One brand kit in full' and then a single dense sentence that maps the return payload; the parenthetical field lists are informative rather than filler. It is long but nearly every clause carries payload semantics.

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 carries the return-shape burden and does so thoroughly — it names the four top-level sections, explains derived nulls and contrast warnings, and states the auth scope. An agent has enough to call it and interpret the result; only not-found behavior is unstated, which is minor.

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% and the single parameter already documents its pattern and points to list_brand_kits for discovery. The description adds nothing about themeId beyond what the schema says, so the 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?

States a specific verb+resource ('One brand kit in full') and enumerates the four payload sections it returns (settings, kit document, resolved colors, knowledge kit), which is far more specific than the bare name. The read-one vs list-many distinction with list_brand_kits is only implied via the parameter description, not stated in the description text.

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?

There is no explicit 'use when'/'don't use when' guidance or named alternative; usage is inferred from the required themeId and the description's content inventory. The 'Requires: demos:read' line gives a useful precondition but not selection guidance.

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