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

Annotations already declare readOnly, idempotent and non-destructive, so the bar is lower; the description adds genuinely new behavior — omitted name resolves to the default kit, a missing kit returns an explanatory message plus a brand-neutral fallback instruction, and it is free. Only the 'read only' clause restates the annotation.

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 purpose and the pre-design recommendation, then packs the return contents into one dense sentence. Slightly run-on and the trailing 'Free and read only' partially duplicates the annotation, but there is little waste.

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?

There is no output schema, so the description must carry the return-value burden — and it does, describing colors, fonts, look, voice and asset links in usable detail, plus empty-state behavior. An agent has everything needed to call and interpret this tool.

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 both parameters are already documented; the description's 'With no name it reads your default kit' merely restates the name parameter's own description and it says nothing about kit_id or the name-vs-id precedence. Baseline 3 is correct.

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 (read) and resource (brand kit) and then enumerates the contents returned — colors with roles, fonts with file links, light/dark preference, brand voice, logo/image links. That detail makes it unmistakable against siblings like list_brand_kits or save_brand_kit without needing their 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?

Explicitly says to read the kit 'before you design, animate or write anything for your brand,' which is clear when-to-use guidance, plus fallback behavior when no kit exists. It never names list_brand_kits as the alternative for discovering which kits exist, so routing between the two read tools is left partly to inference.

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