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

Annotations already flag destructiveHint=true, and the description backs that up concretely: it OVERWRITES existing copy, keeps no prior wording, refuses invented tokens, and silently truncates with a warning at twice the slot max. These are exactly the consequences an agent needs before committing a write.

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?

Front-loads the action in the first sentence, then layers token provenance, copy-matching, length limits, and the overwrite warning. Dense but every clause carries operational meaning; minor redundancy in repeating the uichemy_get_page reference.

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 write with no output schema, the description covers inputs, failure modes, and data loss. It stops short of saying what a successful call returns (e.g., which slots were updated or which warnings fired), which would fully close the loop.

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 only 50% (projectId is undocumented), but the description compensates by explaining the text map's keys as fixed text_ tokens sourced from uichemy_get_page, why invented tokens fail, and how slot label/sample should shape the value. Length behavior (kept-with-warning vs refused) further clarifies what values are valid.

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 ("Replace the copy in one or more text slots") with batch semantics made explicit. It does not, however, distinguish itself from close siblings such as uichemy_replace_text or uichemy_get_text, leaving the agent to infer which text-editing tool applies.

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 clear prerequisites (tokens must come from uichemy_get_page or the uichemy_create_project reply) and a conditional rule for reading old text first when the user may want it back. No explicit exclusion versus the similarly named uichemy_replace_text, so it stops short of full when-not guidance.

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