List posts

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the bar is lower. The description still adds real signal: newest-first ordering, page cap of 50, cursor round-trip semantics, and that scheduled posts carry a publish time.

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?

The opening line is immediately echoed by the first sentence ("Posts of your publication, newest first" / "Lists posts of your publication, newest first"), which is wasted space. The remaining pagination and status notes are well front-loaded and earn their place.

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 it does reasonably: status, audience, ordering, and the scheduled publish time. Pagination is covered; per-post fields are only sketched, not enumerated.

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 schema already documents limit, cursor, and the status enum with defaults. The description restates the same defaults and the cursor pattern rather than adding new parameter nuance; baseline 3 applies.

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 of your publication") plus the ordering and returned fields. It is unambiguous against siblings like get_post or list_notes, though it never names an alternative explicitly.

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 clear context for the key filter ("Filter by status to see drafts or scheduled posts") and explains the pagination loop. It stops short of explicit when-not-to-use guidance or pointing to 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.