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

Annotations already carry destructiveHint=true and readOnlyHint=false. The description adds valuable behavioral context by specifying what kinds of items are deleted and requiring user confirmation before deleting potentially real data. It aligns with the annotations and adds the confirmation policy beyond the structured metadata.

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 sentences, each earning its place: first defines the operation and scope, second gives the use cases, third provides the prerequisite and confirmation requirement. The most important information is front-loaded.

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 simple two-parameter delete operation with destructiveHint and idempotentHint already in annotations, the description covers what is deleted, when to use it, where to get the id, and the confirmation policy. No critical guidance is missing.

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%, with both id and type already documented in the schema. The description repeats the type options and id source but does not add meaning beyond the schema. This matches the baseline for full schema coverage.

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 uses a specific verb ('Delete'), names the resource ('profile item'), and enumerates the exact types it applies to: work experience, project, education. It clearly distinguishes itself from siblings like delete_linktree by scoping to profile items.

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 gives explicit when-to-use context: 'clean up duplicates, placeholder/test entries, or clearly wrong data.' It also provides a prerequisite ('Get the id from get_profile') and a safety rule ('Always confirm with the user before deleting anything that could be real'). It lacks explicit when-not-to-use or named alternatives, but the context is clear enough.

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