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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds value beyond that by requiring user confirmation before deleting anything that could be real, which is behavioral guidance the annotations cannot express.

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 tight sentences: purpose and variants first, then usage triggers, then the safety caveat. No filler, though the parenthetical about 'type accordingly' slightly duplicates the schema's enum documentation.

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 mutation with full annotation and schema coverage and no output schema, the description supplies the missing pieces an agent needs: id provenance, the type-to-item mapping, and a confirmation requirement. Nothing critical is absent.

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 the enum and the id pattern/24-hex constraint already documented in the schema. The description restates that ids come from get_profile and that type must match the item kind, adding little beyond the structured fields, so 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 (delete) plus the resource (profile item) and enumerates the three concrete variants (work experience, project, education), telling the agent to set type accordingly. This clearly separates it from the save_*/update_profile siblings that operate on the same resources.

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 concrete when-to-use triggers (duplicates, placeholder/test entries, clearly wrong data) and names the prerequisite source for ids (get_profile). It stops short of explicitly naming a when-not or an alternative tool, but no sibling can delete profile items, so the routing gap is minimal.

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