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

Annotations declare read-only/non-destructive, and the description adds substantial behavior: it returns every component file plus an App.jsx and a stylesheet-download command, unfilled slots fall back to template sample copy, files are meant to be used as-is with styling coming from the kit, and photos are searched server-side, so no separate image search is needed.

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 core action and routed alternatives early, and dense with useful detail. Slight redundancy in the closing 'copy and image urls can be changed afterwards by editing the files' which restates the earlier 'rewrite the copy by editing the files'.

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?

No output schema exists, but the description fully covers the return shape (component files, App.jsx, stylesheet command, slot metadata per file) and default behaviors, which is everything an agent needs to invoke and consume 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 coverage is 100%, so baseline is 3; the description nonetheless adds real meaning: `text` is slot-token→copy, `photos` is per-section queries with a page-wide default, and palette/fonts are page-level. It clarifies the relationship between the per-section photos and the top-level photos default, which the schema only hints at.

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 (builds a page of React app code from UiChemy sections) and explicitly contrasts with uichemy_create_project for projects and implies get_template_code territory. An agent can distinguish it from siblings without opening the 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?

Explicitly says when to use this tool vs uichemy_create_project, and names the discovery path (uichemy_find_templates / uichemy_search_layouts to pick layouts, uichemy_list_templates to enumerate a kind's layouts). No inference required.

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