list_posts

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

The description states 'Read-only' which signals non-destructiveness, but provides no additional behavioral details such as pagination, rate limits, or authentication requirements. With no annotations, the description carries the burden but only partially satisfies it.

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?

Two sentences: first sentence defines purpose and default, second sentence lists alternatives. No unnecessary words, front-loaded with key info.

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 listed list tool with 3 parameters and no output schema, the description covers the essential: purpose, default, and when to use alternatives. It lacks details on pagination and parameter format, but given the simple context, it is nearly complete.

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. It explains the 'pub' parameter implicitly (publication, default yours) but does not clarify 'limit' or 'sort' beyond their names. Some value is added, but not enough for full understanding.

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?

Description clearly states 'list posts from a publication' with a default scope, and explicitly names sibling tools (get_post, get_post_content, search_posts) for alternative purposes, providing strong differentiation.

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 includes explicit when-to-use guidance: 'For a single post by id/slug use get_post; for full HTML body use get_post_content; to find by keyword use search_posts.' This helps an agent avoid misuse.

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