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

Annotations already cover safety (readOnlyHint, idempotentHint, non-destructive), so the description's job is to add behavioral detail — and it does: results are ordered "newest first" and each post is returned "with its media", disclosing both ordering and payload shape. Pagination behavior via starting_after/next_cursor is left unmentioned, which is a modest gap but not fatal.

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, front-loaded with what the tool returns, then scope, then the most actionable status semantics. No filler and nothing redundant with the schema.

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 carries the burden of describing returns and does so adequately (ordering plus media inclusion). The main omission is pagination semantics — that starting_after takes the previous page's next_cursor is only in the schema, and the description never signals cursor-based paging.

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 100%, so the baseline is 3, and the description genuinely adds meaning by explaining what two status values signify operationally (scheduled = the queue, failed = needs attention) beyond the schema's vague "Where the post is." It does not interpret the remaining status values or the platform/post_type enums, so it falls short of a 5.

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 clear verb and resource ("List posts") and narrows scope to "Content Studio posts", which is more specific than the bare name. It does not, however, distinguish itself from the sibling list_recent_posts, so an agent cannot tell from the description alone which of the two list endpoints to pick.

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 line "status=scheduled is the queue, status=failed needs attention" gives practical interpretation of two status values, which is real usage guidance. But there is no explicit when-to-use/when-not guidance and no mention of the near-duplicate sibling list_recent_posts or get_post for single-post retrieval.

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