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

With no annotations, the description carries the full burden. It discloses key behavior: returns only 'published' posts, orders by 'most recent', and limits to 'N'. It does not mention side effects, but 'return' implies a read-only operation. The description adds useful context (publishing status, recency) beyond 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, front-loaded sentence that conveys the essential purpose and scope without waste. It earns its place with every word.

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 one-parameter tool with an output schema present, the description adequately covers the main behavior (returning recent published posts up to a limit). It does not detail return format, but that is covered by the output schema. Missing guidance on alternative tools is minor given the simplicity.

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?

The schema has no descriptions (0% coverage). The description uses 'N' to represent the limit, conveying that the limit controls the number of returned posts, but it does not explicitly reference the parameter name 'limit' or its range (schema provides min/max/default). This adds some meaning but leaves the mapping implicit.

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 states a specific verb ('return') and resource ('blog posts'), with clear scope ('most recent published') that distinguishes it from siblings like get_post (single post) and search_posts (search). The title and description align well.

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 usage for listing recent published posts via 'most recent published,' making it clear when to use this tool. However, it does not explicitly mention alternatives or exclusions, such as recommending search_posts for filtering or get_post for a single item. Since sibling names are available, the context is sufficient though not explicit.

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