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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: results are ordered newest first and the payload is deliberately truncated to the first line, which would otherwise cause an agent to work from partial content. No pagination totals or caps are mentioned, but limits live in the schema.

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?

Three short sentences, zero filler, and the core behavior (lists, newest first, truncated) is front-loaded before the usage guidance and the get_post handoff.

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 no output schema, the description still tells the agent what comes back (first line of each post) and where to go for the untruncated version. Combined with the annotations and a fully documented schema, an agent has everything needed to call this correctly.

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 100%, and the schema itself documents limit, offset and the status values, so the baseline applies. The description only indirectly touches offset semantics via 'newest first' and adds nothing about the status filter or how truncation interacts with paging.

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 and resource (lists posts in this workspace) plus two distinguishing traits: newest-first ordering and truncated first-line content. It explicitly separates itself from get_post, which returns the full text, so an agent can pick the right tool 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?

Gives an explicit use case ('use it before writing to check what has already been said') and an explicit alternative for the fuller operation ('to work on a post, read it with get_post first'). It does not address other listing siblings such as list_top_posts or scrape_posts, so the routing is clear but not exhaustive.

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