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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is covered. The description adds genuinely new context beyond them: the cascade behavior (AI-suggested and rejected prompts are deleted with it) and a named failure mode (TOPIC_HAS_PROMPTS) with a recovery step. Return values and idempotency confirmation are not addressed, keeping it just under the top mark.

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?

Two sentences with a parenthetical, zero waste, and the core action is front-loaded ahead of the failure condition and cascade caveat. Every clause earns its place.

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?

No output schema exists, so the description must carry behavioral burden, and it does: precondition, error code, and cascade destruction are all stated. It is largely complete; only explicit guidance on non-active prompts or confirmation behavior 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%, so both parameters (id, workspaceId) are already documented in the schema. The description adds no parameter-level meaning beyond what the schema provides, which is the baseline 3 when the schema carries the load.

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+resource ('Delete a topic') that cleanly distinguishes it from siblings like create_topic, update_topic, and list_topics. The purpose is unambiguous without opening the schema.

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 a clear precondition and remediation path ('pause or re-assign them first') when TOPIC_HAS_PROMPTS is hit. It stops short of naming an explicit alternative sibling (e.g., update_topic or delete_prompt), so it's strong context rather than full when/when-not routing.

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