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

Annotations declare destructiveHint=true and readOnly=false, and the description adds nothing about that behavior — it never says whether an existing description is overwritten, appended to, or whether the prior value is recoverable. The one piece of useful context it gives is downstream consumption by generation, which is genuinely beyond the annotations, but the mutation semantics an agent most needs are absent.

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 tight sentences with the core action front-loaded and the disambiguation in a clause rather than a paragraph. Every element earns its place; slight density in the opening sentence but 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 and a destructive mutation, the description covers purpose and one sibling distinction but leaves the overwrite behavior and all three parameter meanings undocumented. Adequate to identify the tool, insufficient to call it safely without inspecting the schema.

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% for three required parameters, so the description must carry the load. It only indirectly explains 'description' ('what the page is for and what it should cover') and says nothing about pageName format, projectId, or the 1000-character cap — an agent could easily pass a slug where a display name is expected.

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 ('Set the note on a page in the site map') and immediately defines what that note contains ('what the page is for and what it should cover'). It explicitly contrasts itself with uichemy_set_page_settings metaDescription, so an agent can distinguish it from the near-identical SEO sibling 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?

Names the exact alternative to use for SEO meta descriptions and states who consumes the value ('Generation and the agents read it'), which tells the agent when this field matters. It stops short of stating prerequisites (project must exist, page must not be published) or when not to call it at all.

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