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

No annotations are provided, so the description carries the full burden. It discloses only the result ordering (=new) and nothing about read-only nature, pagination behavior, result shape, or any limits — insufficient for a 5-parameter list tool.

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 front-loaded sentence with zero padding or redundancy. It is efficient, though its brevity reflects under-specification more than deliberate concision.

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?

With 5 parameters at 20% coverage, no annotations, and no output schema, the description should explain what the tool returns and how the filters behave. A one-line alias pointer leaves the agent unable to call it confidently without inspecting list_threads.

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 only 20% (just the format enum), so the description needs to compensate for limit, since, topic, and until — and it says nothing about any of them. The 'sort=new' note hints at ordering but is not one of the tool's parameters.

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 defines the tool purely by reference to another tool ('Alias of list_threads (sort=new)') rather than stating what it actually returns. An agent that knows list_threads can infer meaning, but the resource itself ('posts') is never described, and it only distinguishes itself from siblings indirectly.

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 alias relation implies a usage rule: this is the newest-first view, so it is interchangeable with list_threads when sort=new. That is useful implied guidance, but there is no explicit when-to-use/when-not statement or any prerequisite, so it stays at 'implied usage'.

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