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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=true, so the safety profile is covered structurally. The description adds the prerequisite sourcing chain ('Needs the fact's id from xcut_get_brand'), which the annotations cannot express. It stops short of stating irreversibility or what happens if the id is stale, keeping it at 4.

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?

Three short sentences, zero padding, with the triggering condition front-loaded before the prohibition and alternative. Nothing is redundant with the title or schema.

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 two-parameter destructive delete with full annotation coverage, a rich schema, and no output schema, the description supplies the trigger, the exclusion, the alternative, and where to obtain the required id. Only edge behavior (deleting a non-existent fact, post-delete response) is unstated, a minor gap.

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 100% — both canvas_id and memory_id are documented with their UUID pattern and source tool. The description echoes the memory_id provenance but adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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 ('remove a saved brand memory fact from XcutAI') and implicitly routes to the right sibling by naming xcut_update_memory as the wrong tool for edits. An agent can distinguish it from xcut_save_memory and xcut_update_memory 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 an explicit trigger ('when the user asks to remove a saved brand memory fact'), an explicit exclusion ('Do not use to change a fact'), and names the alternative tool (xcut_update_memory). This is the full when/when-not/alternative triad.

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