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

Annotations already declare destructiveHint=true, readOnlyHint=false, and idempotentHint=false, so the risk profile is covered. The description adds meaningful context beyond annotations by disclosing that the deletion cascades to 'everything derived from it' and by prompting the agent to name the target first.

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, front-loaded with the destructive scope and followed by the key pre-deletion caution. Every sentence earns its place without repetition.

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 one-parameter delete tool with rich annotations and full schema coverage, the description covers the critical cascade behavior and cautions the agent before acting. It does not explain return behavior, but no output schema exists and the omission is minor for a destructive 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 100%, and the itemId parameter is already documented as coming from list_knowledge or search_knowledge. The description adds no further parameter meaning, so the baseline 3 is appropriate.

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?

The description states a specific verb and resource: 'Removes a stored item and everything derived from it.' The cascading scope distinguishes it from a simple row deletion, though it does not explicitly differentiate itself from sibling delete tools such as delete_post or delete_project.

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 only procedural guidance is 'Name what you are about to delete first,' which is a caution rather than a when-to-use rule. It gives no explicit alternatives, prerequisites, or conditions for choosing this tool over list_knowledge or search_knowledge.

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