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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description adds the consequences annotations cannot express: prompts are kept and become topic-less, subtopics are promoted to top-level, recorded answers survive, execution is immediate and irreversible. That is exactly the extra context needed before a destructive call.

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?

Front-loaded with the verb and its condition, followed by the data-retention effects, the irreversibility warning, and the alternative routing. Every clause carries distinct information; nothing is padding.

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, non-idempotent tool with no output schema, the description covers preconditions, side effects on related entities, reversibility, and alternatives. An agent has everything required to call it correctly and safely.

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 100% and both parameters are documented in the schema (name, case-insensitive; project_id from list_projects). The description only restates 'by name' and adds no format or constraint detail beyond the schema, so the baseline 3 applies.

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 one topic by name) with scope (the grouping itself), and explicitly contrasts itself with rename_topic and prepare_archive_prompts. An agent can distinguish it from create_topic and rename_topic without opening any 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 an explicit precondition ('after the user agrees'), an explicit trigger ('when the grouping itself is no longer wanted'), and routes two adjacent needs to named alternatives: rename_topic for renaming and prepare_archive_prompts for ceasing measurement.

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