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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true, and non-idempotency, so the safety profile is structured. The description adds only the deprecation window, with nothing about what gets removed, whether removal is reversible, or what happens to replies attached to the post.

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?

A single tight sentence with the deprecation status front-loaded ahead of the replacement pointer. No filler, no repetition of the tool name.

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, open-world mutation with an undocumented parameter and no output schema, the definition supplies only a deadline. An agent still cannot tell what the tool actually does or how to form the 'thread' argument, which is a large gap even granting that the tool is being retired.

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?

There is one required parameter, 'thread', with 0% schema description coverage, and the description says nothing about it — no format, no ID vs slug distinction, no note on cascade effects. With low coverage the description should compensate, and it does not.

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 never states what the tool does; it only announces deprecation and points at node_remove. An agent must infer from the name 'trana_unpost' and the sibling set that this removes a trana post. Acting as a redirect is useful, but the verb+resource is never given.

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?

It explicitly names the replacement (node_remove) and gives a hard cutoff date (2026-11-10), which is the routing decision an agent needs for a deprecated tool. It stops short of saying whether existing callers should migrate immediately or whether this still works for legacy threads, but the alternative is unambiguous.

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