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

Annotations only cover the generic read-only/closed-world profile. The description adds real behavioral context: the three return sections (brief, css, tokens), the fact that interfaces already link css as brand.css so callers should use var(--brand-*) rather than hex, that the brief carries the reasons behind each rule, and that before any kit exists it returns workspace colors with kit: null. That is meaningful disclosure beyond the annotations.

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 purpose, then the when-to-use directive, then the return breakdown, so the important material leads. It is dense and packs several ideas into one sentence, but with no output schema each clause carries information an agent needs, so little is wasted.

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 and only two optional parameters, the description carries the burden of describing returns and does so thoroughly: the three fields, their shapes (markdown brief, --brand-* variables, resolved tokens), the consumer convention for css, and the no-kit fallback with kit: null. An agent has enough to call it and interpret the result.

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%, so the schema already documents both kitId (sourced from napkin_brand_list, omit for workspace brand) and workspace (slug, required for personal tokens without a default, ignored for API keys). The description's 'unless you name another' largely restates the kitId default rather than adding format or constraint detail, 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?

The description gives a specific verb and resource ('Reads a brand kit') plus a clear default scope ('the workspace's brand unless you name another'), and it routes to napkin_brand_list as the source of kitId. It does not, however, distinguish itself from sibling napkin_brand_view, which could plausibly also read a brand, leaving one ambiguity unresolved.

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?

Usage is stated forcefully and concretely: 'READ THIS BEFORE writing or designing anything for the workspace: a deck, a doc, an interface, copy.' It also names napkin_brand_list as the way to obtain a kitId. It stops short of stating when not to call it (e.g., when the brief is already in context), so it is clear context without exclusions.

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