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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description doesn't need to restate those. It adds valuable behavioral context: the operation is restricted by role, blocked by in-progress capture analysis, and blocked by active automations because they hold setup answers and Policy context notes. This goes beyond the annotations and helps the agent anticipate failures.

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?

The description is a single, information-dense sentence that front-loads the core action and then packs the key constraints and rationale. Every clause earns its place; there is no filler or 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 single-parameter tool with no output schema, the description covers the essential context: who can delete, what blocks deletion, and why automation must be removed first. It doesn't describe the return value or side effects on related data, but the annotations and simple parameter schema make that a minor gap.

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 single parameter 'id' is already described as 'Clarity process id' with a UUID format and pattern. The description adds no additional parameter-level meaning beyond what the schema provides, so the baseline of 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 ('Delete') and resource ('a Clarity process'), and clearly distinguishes it from sibling tools like deleteClarityProcessLabel, deleteClarityProcessLink, and deleteClarityProcessInviteLink. It also adds scope by naming who can delete and under what conditions.

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 explicitly states when deletion is allowed (creator or team admin) and when it is not allowed (capture analysis in progress, or an automation still runs it). It also explains the dependency that automation must be removed first, giving the agent actionable guidance for handling a blocked deletion.

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