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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely new consequence detail: a draft/sample/watched page is never re-imported while a pasted piece is deleted, which tells the agent how permanent the effect is per source type.

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 sentences, front-loaded with the destructive scope, then the source-type consequence, then the confirmation prerequisite. No filler and no repetition of the title.

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 two-parameter tool with no output schema, the description covers scope, permanence by source type, and the user-confirmation requirement. The remaining gap is the undocumented profile_id parameter and any indication of what the caller gets back after the delete.

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 carries the burden for both parameters. It usefully explains where item_id comes from (get_memory) but says nothing about profile_id, leaving one of two required parameters with no semantics in either place.

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 ('Forget a whole piece ... and every memory taken from it') and clarifies the unit of deletion, which distinguishes it from the sibling delete_memory that acts on a single memory. The parenthetical 'item_id from get_memory' ties the input to the tool that produces it.

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 prerequisite ('Confirm with the user first') and the scope rule that makes this the right tool when an entire piece, not one memory, is being removed. It does not name delete_memory as the alternative for single-memory removal, so the routing is implied rather than stated.

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