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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds the 'newest first' ordering trait, which is useful, but says nothing about pagination, caps, or return format.

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 resource and ordering and no wasted phrasing. The trailing 'after a timeout' clause is slightly cryptic but does not bloat the text.

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 read-only list tool with annotations already covering safety and no output schema to explain, the definition is nearly sufficient. It still omits how results are paginated and how it relates to the get_post sibling, leaving minor gaps.

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 coverage is 50%: limit is documented in the schema but status only exposes an enum without prose. The description partially compensates by mentioning a status filter, but adds no syntax or default details for limit beyond the schema.

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 names the resource (posts), the ordering (newest first), and the optional filter (status), so the agent knows what the tool returns. It does not, however, distinguish itself from the sibling get_post, which an agent might reasonably confuse for post retrieval.

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?

'Use it to find a post after a timeout' gives one concrete when-to-use scenario, but it is narrow and offers no guidance against alternatives like get_post or list_channels. Usage is implied for listing scenarios but not framed as a choice.

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