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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the one thing annotations cannot express: the delete is non-cascading and child prompts are retained, which materially changes the agent's risk assessment. It still omits irreversibility and any permission requirements.

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 short sentences, no filler, with the destructive action stated first and the side effect second. Nothing is padded or repeated from 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, three-identifier mutation with no output schema and no annotation-level detail about scope, the description carries real gaps: it never says whether deletion is recoverable or how project/site/topic scoping works. The non-cascade note is the single most important fact and it is present, which keeps this at minimum-viable rather than inadequate.

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 0% across three required parameters (projectId, siteId, topicId), and the description explains none of them. Only topicId is loosely implied by the word "topic"; the other two identifiers, and why all three are needed, are undocumented in both places.

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?

"Delete a topic" gives a specific verb and resource, and "Its prompts are kept" separates it from sibling delete_ai_visibility_prompt by making clear this removes the container, not its prompts. It stops short of naming the sibling explicitly, so it is clear but not fully disambiguating in a 150-tool list.

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 when-to-use framing, no prerequisites (e.g. required project/site scope), and no pointer to delete_ai_visibility_prompt for removing individual prompts. The only guidance an agent can infer is from the side note that prompts survive the delete.

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