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

Annotations only declare the write-safe profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false); the description adds two real behavioral facts the schema does not: the draft is seeded from the current published version, and an already-open draft is returned instead of a duplicate. That second point sits in mild tension with idempotentHint=false, but it reads as a disclosed dedupe behavior rather than a contradiction, and it usefully prevents the agent from retrying to force a fresh draft.

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 short sentences with no filler; the core action is front-loaded and the dedupe behavior follows as supporting detail. Nothing here is redundant with the title or the annotations.

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, the description usefully indicates what the caller receives (an editable draft, or the pre-existing one). It does not cover permissions, what happens when no published version exists, or the shape of the returned draft, which are the remaining gaps for a write tool.

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%, so the description must carry parameter meaning, and it largely does not. It implies which ICP is targeted (the one whose published version is drafted) but never explains why icpId is a UUID reference, and the optional nested 'body' object is never mentioned at all.

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 ('Creates an editable draft of an ICP') plus its source ('from its current published version'). That distinguishes it implicitly from createIcp, createManualIcp, and createIcpFromScan, though no sibling is named explicitly.

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?

The description implies when this tool is appropriate (an ICP already has a published version to draft from) but never states exclusions or names alternatives such as createIcpFromScan or createManualIcp. The agent must infer the routing decision from sibling names alone.

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