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

The description describes an irreversible deletion ('Delete your own content'), while the annotations declare destructiveHint=false and readOnlyHint=false, so the declared safety profile directly contradicts the stated behavior. The useful precondition text does not resolve this mismatch, and the description offers no disclosure of whether the removal is a hard delete, a soft delete, or recoverable.

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, front-loaded with the action and the scope, with the allowed kinds and the blocking conditions each appearing once. It is terse to the point of being skeletal, but no sentence is wasted and nothing is buried.

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?

The output schema exists, so return values need no explanation, and the blocking conditions are covered. However, for a mutation tool with 0% schema description coverage across three required parameters, the definition does not say whether the delete is permanent or what the caller gets back on a blocked attempt, which is a meaningful gap.

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% and there are no enums, so the description carries the load — it does supply the legal values for `kind` (thread, post, pit), which is the single most useful thing it could add. It says nothing about `content_id` format (numeric id vs slug vs UUID) or what `api_key` must be, leaving two of three parameters undocumented anywhere.

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 your own content'), scopes ownership, and enumerates the accepted kinds ('thread | post | pit'), which is the key disambiguator against edit_content and read_thread. An agent can tell exactly what the tool does 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?

Adds a real precondition — deletion is blocked for a thread with an open bounty or a reply that won one — which is the kind of when-not guidance most definitions omit. It never names a fallback such as edit_content for content that cannot be deleted, so it stops short of full routing guidance.

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