Delete a forum thread

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

Adds substantial behavior beyond annotations: auth requirement, ownership constraint, irreversibility ('cannot be undone'), and non-idempotent error behavior on repeated deletes. This enriches the destructiveHint and idempotentHint annotations.

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 front-loaded sentences with no filler. First sentence states the action and scope; second sentence covers consequences and error behavior.

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 simple one-parameter destructive delete, the description covers auth, ownership, ID source, irreversibility, and repeat-call behavior. Output schema exists, so return value documentation is not required.

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 already fully documents the id parameter with type and description ('AniList thread ID to delete'). The description adds value by explaining the ID can be obtained from search_thread, get_thread, or post_thread, clarifying provenance.

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?

Description clearly states the verb ('Delete'), resource ('forum thread'), and specific scope ('the authenticated user owns'). It also specifies the required input mechanism (by its ID) and distinguishes from siblings like delete_thread_comment by focusing on threads.

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?

Provides clear context: requires login, ownership, and sources for the ID (search_thread, get_thread, post_thread). It does not explicitly name alternative tools or exclusions, so it stops short of full when-to-use guidance.

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