List published posts

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

Annotations already convey read-only, idempotent, open-world, and non-destructive behavior, so the safety profile is covered. The description adds only the 'newest first' ordering behavior and doesn't mention pagination or default-publication behavior, though those are largely documented 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?

The description is a single six-word sentence that leads with the action and object and adds one meaningful qualifier. There is no filler or redundant restatement beyond the title.

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 listing tool with strong annotations and well-documented optional parameters, the description is nearly sufficient. It could be more complete by explicitly distinguishing list_posts from list_reader_posts or search_posts, but the 'publication' parameter and read-only annotations provide enough context for correct invocation.

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?

With 60% schema description coverage, the schema already documents limit, offset, and publication clearly; order_by and order_direction have self-explanatory enums and defaults. The description's 'newest first' reinforces the default order but adds no new parameter meaning beyond the schema.

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 names a specific verb ('List') and resource ('published posts') and adds a clear ordering contract ('newest first'). This is enough to distinguish it from siblings like list_drafts, list_scheduled_posts, and search_posts without needing to open 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?

The description implies the tool is for retrieving published posts in chronological order, which gives basic usage context. It does not explicitly say when to prefer search_posts, get_post, or list_reader_posts, nor does it state any exclusions.

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