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

readOnlyHint=true already declares this is a safe read, so the description carries a lighter burden, but it adds almost nothing beyond the structured data: no ordering, no result count or pagination behavior, no indication of what "this account" resolves to. Account scoping is the only behavioral signal, which is thin for a list endpoint that could return many rows.

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 the resource and scope first and the filter modifiers after. No filler, no restatement of the tool name as a standalone clause.

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?

There is no output schema and no annotations beyond readOnlyHint, so the description is the only place pagination, ordering, and result shape could be surfaced for a list endpoint — and none of it is. An agent cannot tell whether it must page, how many results to expect, or whether both filters can be combined.

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 0%, so the description must compensate, and it does partially by identifying both parameters as optional filters and naming what they filter (status, platform). The enum values themselves are self-documenting in the schema, but the description adds no semantics about combining filters or default behavior when omitted.

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 ("List posts") scoped to "this account", which distinguishes it from the singular get_post sibling. It does not explicitly mention the create/update/delete siblings, but the read-list verb plus account scoping makes the intent unambiguous.

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?

"Optionally filtered by status or platform" implies the two usage modes, and the contrast with get_post is inferable from "List" vs a single-record fetch. However, there is no explicit when-to-use guidance, no statement that all posts are returned when no filter is given, and no pointer to alternatives such as get_post_stats.

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