delete_forum_topic

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds important behavioral context by stating 'along with all its messages,' disclosing that the operation cascades to delete all contained messages. This goes beyond the annotations and clarifies the full destructive impact.

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 concise sentence that is front-loaded with the action and resource. Every word contributes meaning, with no filler or redundancy.

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?

Given the tool's simplicity (only 2 required parameters, complete schema coverage, and clear annotations), the description adequately covers the essential context: it identifies the action, the target, and the cascading effect on messages. No output schema exists, and none is needed for this straightforward deletion operation.

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?

The input schema already provides 100% parameter description coverage: chat_id is 'Chat ID or @username' and message_thread_id is 'Forum topic thread ID'. The description does not add additional parameter-level meaning beyond what the schema already documents, so the baseline score 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 uses a specific verb and resource: 'Delete a forum topic along with all its messages.' It clearly states the action and scope, distinguishing it from sibling tools like delete_message/delete_messages (which delete individual messages) and close_forum_topic (which closes rather than deletes).

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 implies when to use the tool: when you want to permanently remove a forum topic and its messages. However, it does not explicitly mention alternatives or when not to use it, such as using close_forum_topic instead if the topic should be preserved but hidden.

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