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

Annotations only declare the safe-read profile; the description adds substantial behavior beyond that: the file depends only on React, colours are optional props defaulting to the style kit, the stylesheet prerequisite, the files are meant to be used as returned, and photos are searched server-side from free-licence stock so no separate image search is needed. It also notes copy and image URLs are editable afterwards. This is exactly the added context the annotations cannot carry.

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 purpose and then dense but mostly load-bearing detail. A couple of statements overlap (the stylesheet prerequisite and 'styling comes from the kit'), and the run-on middle sentences could be tightened, but nothing is filler.

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 7-parameter code-generation tool with no output schema, the description covers the key unknowns: prerequisites, image-resolution behavior, and editability of the result. It could say more about what is actually returned (single file vs files, naming, where the componentName lands), which is the one remaining 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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning: text keys are slot tokens cross-referenced to uichemy_template_slots, photos are natural-language queries resolved server-side against free-licence stock (one query per picture, in order), while images are direct slot→url overrides. The photos-vs-images distinction and server-side search behavior are not obvious from the schema alone.

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?

Opens with a specific verb+resource+scope: 'One UiChemy library section as a standalone React + Tailwind component for the user's own React app.' It explicitly contrasts itself with uichemy_get_page_code ('returns a whole page in one call'), so an agent can route between the two without opening either schema.

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 real routing context: use this for one section, get_page_code for a whole page; pass text via uichemy_template_slots tokens; the output needs the stylesheet from uichemy_get_style_kit. It stops short of an explicit 'do not use this when…' rule, but the when-to-use signals are clear and actionable.

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