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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: it is a prerequisite read for mutation tools, and imported projects are governed by different rules than generated ones – useful behavioral information not derivable from 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?

Two sentences, front-loaded with the scope of what is inspected. The second sentence is information-dense about sequencing and import rules. Slightly long, but each clause earns its place; no 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?

With no output schema, the description correctly carries the burden of listing what is returned, and it does so thoroughly. Combined with annotations covering the read-only nature and the usage note that it precedes mutations, an agent has enough to call it correctly; only an explicit alternative path is missing.

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 projectId parameter is documented in the schema ('From uichemy_list_projects, or the id in the editor url'). The description adds nothing about the parameter, 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 ('Look INSIDE') and resource (a UiChemy project) and enumerates exactly what comes back: pages in order, sections, palette, fonts, button/card designs, import provenance. That scope implicitly separates it from narrower siblings like uichemy_get_page or uichemy_get_style_kit, but no alternative is named explicitly, so it stops short of a 5.

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?

Explicit when-to-use: 'Call this before changing anything', with a stated rationale (the design tools need current values to describe replacements). It also flags a conditional behavior (imported vs generated projects follow different rules). What it lacks is a named alternative for the case where only a slice of project data is needed.

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