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

Annotations already flag mutation and destructiveHint=true; the description adds non-obvious behavior: an empty href restores the template's own link, and a key belongs to the LAYOUT so a shared navbar propagates the change to every page. It stops short of stating that an existing link is overwritten or what projectId scoping means.

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?

Dense but front-loaded: the core action leads, followed by key semantics, accepted href formats, edge case, and layout scope. Every sentence carries distinct information, though it is on the long side.

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 mutating, no-output-schema tool, the definition covers the action, key provenance, valid value formats, and the layout-wide blast radius. The remaining gap is the undocumented `newTab` parameter and the exact overwrite semantics behind destructiveHint.

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?

With only 25% schema coverage, the description does heavy lifting: it defines the `key` slot convention and enumerates accepted href forms (https://, /path, #anchor, mailto:, tel:, empty-to-restore). However, `newTab` and `projectId` remain undocumented in both schema and description.

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 ('Point a button or text link somewhere') and frames it as the editor's Link control, which no sibling covers. It distinguishes itself from the listing tool by pointing to uichemy_list_links for key discovery.

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?

Explains the two key shapes (label slot `text_…` vs icon-only icon slot `icon_url_…`) and routes the agent to uichemy_list_links to find them. It gives clear context but does not state explicit exclusions or when not to use it.

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