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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious context: the faults are silent (no error raised) and 'invisible until somebody opens the right page on the right surface'. It says nothing about cost/runtime or output shape, but with annotations doing the safety work this is above the 3 baseline.

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?

The core purpose is front-loaded in the opening clause, and the closing sentence carries the actionable directive. The middle is a single sprawling sentence listing nine fault types, which is informative but verbose and tilts toward purple prose ('which is why an agent should run this...').

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 simple 1-parameter read-only tool the fault taxonomy is thorough, but with no output schema and no return-format hint, an agent cannot anticipate what validation results look like, and the sole input parameter is left undocumented. Two real gaps keep it at minimum-viable completeness.

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?

One parameter (projectId) with 0% schema description coverage, and the description never mentions it. projectId is a near-self-evident identifier shared across the sibling set, which keeps this from being a 1-2, but the description does not compensate for the missing schema documentation as the low-coverage rule requires.

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+resource (check the whole project) and enumerates concrete fault classes it detects (stale slots, orphaned overrides, broken blog links). The 'whole project' scope implicitly separates it from narrower siblings like uichemy_check_layouts and uichemy_check_responsive, so an agent can tell them apart without opening a 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 a clear usage trigger: run it 'before telling anyone the work is done', framing it as a final pre-completion gate. It does not, however, name alternatives or state when NOT to use it (e.g. versus check_layouts/check_responsive), so the routing guidance stops short of the 5-level bar.

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