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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds the useful ownership constraint ('the caller's'), implying you cannot remove another user's prompt, but says nothing about permanence or recoverability of a destructive delete.

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 sentence with a front-loaded [write] classification tag and zero filler. The prerequisite reference is embedded rather than padded into extra sentences.

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 destructive delete with rich annotations and no output schema, the definition covers purpose, ownership scope, and how to obtain the ID. Only the irreversibility/undo behavior is left implicit.

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 coverage is 0%, so the description carries the burden — and it does, by identifying the parameter's source (list_character_prompts) which the bare schema does not. It adds no format or validation detail beyond that, so a 4 rather than a 5.

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 pairs a specific verb (delete) with a specific resource (one of the caller's saved studio prompts) and even names the exact identifier field. It is unmistakably distinct from save_character_prompt and list_character_prompts, and the [write] tag pre-classifies the operation.

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?

It tells the agent where the required argument comes from ('characters_prompt_uuid from list_character_prompts'), which is a concrete prerequisite flow. It stops short of stating when not to delete or warning that no undo exists, so it isn't a full 5.

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