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

Annotations already declare destructiveHint=true, but the description goes well beyond that: it enumerates exactly what is destroyed, explains why slot tokens on other pages survive the deletion, states the home-page protection rule, and notes that a report of what was deleted is returned because the action is irreversible. This is unusually rich behavioral disclosure for a destructive operation.

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 destructive scope is front-loaded, which is good, but the middle sentence ('Copy a section on ANOTHER page still renders is kept...') is syntactically tangled and hard to parse, and the closing clause about the caller being able to report the deletion is more editorial than informative.

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 destructive tool with no output schema, the description covers destruction scope, the home-page restriction, cross-page side effects, and the fact that a deletion report is produced. The only real gap is parameter identity (which project, which page), which the schema does not fill either.

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 0% and the description never mentions projectId or pageName, their formats, or how a page is identified. It only implies 'page' generically, so it does not compensate for the undocumented parameters even though the names are fairly self-explanatory.

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 precise verb and resource ('Delete a page') and immediately scopes what 'page' includes: sections, layouts, backgrounds, overlays, padding, copy and pictures. This clearly separates it from siblings like uichemy_remove_section, uichemy_duplicate_page and uichemy_delete_project without opening any 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 real usage boundary — the home page cannot be removed because it is the root of every other page — which tells the agent when this call will fail. It does not name alternative tools (e.g. remove_section for partial teardown), so it stops short of full when/when-not/alternatives guidance.

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