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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered structurally; the description adds nothing beyond restating deletion. It does not say whether the deletion is permanent, whether it cascades to associated leads/keywords, or whether a confirmation is required.

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?

A single short sentence is front-loaded and free of waste, but that brevity comes from under-specification rather than discipline. It is minimally structured but not informative.

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 tool with three undocumented required IDs and no output schema, the description should at least indicate scope and permanence. It leaves the agent without enough to call it safely or correctly.

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?

All three required parameters (projectId, siteId, icpId) have 0% schema description coverage and the description mentions none of them or their scope/format. Unlike a zero-parameter tool, this definition leaves the identifiers entirely unexplained.

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 gives a specific verb ("Delete") plus a resource ("customer profile"), but the resource is named loosely and doesn't match the tool's own title ("ideal customer profile") or the icpId parameter. It also offers no differentiation from the many nearby delete siblings such as delete_lead_keyword or delete_outreach_template.

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?

There is no guidance on when to delete an ICP versus updating (update_lead_icp) or deactivating it, no prerequisites, and no mention of the project/site scope needed. The agent must infer all selection context.

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