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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds the meaningful 'newest first' ordering trait, but says nothing about pagination behavior or how many items come back by default.

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 tight sentences with the return shape front-loaded and no filler. The 'after a timeout' clause is slightly informal but earns its place as usage guidance.

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 with no output schema, the essentials (contents, ordering, optional filter) are present. It omits default/max limits (only in the schema), pagination, and any pointer to get_post for single-record retrieval, so it is adequate rather than complete.

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 50%: limit is documented in the schema, but status carries only an enum. The description confirms status is an optional filter, adding marginal value, but the enum values themselves are what convey the allowed statuses, so the description does not compensate much for the gap.

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 states the resource (posts), the ordering (newest first), and the optional status filter, so an agent can tell it returns a collection rather than a single record. It lacks an explicit verb and does not name the get_post sibling it contrasts with, but the purpose is clear.

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 provides one concrete scenario ('find a post after a timeout'), which is genuinely useful context for the create_post flow. However, it never states when NOT to use it or points to get_post when the ID is already known, leaving the sibling routing to inference.

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