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

No annotations are provided, so the description carries the full burden. The verb 'List' implies a read-only operation and 'published' scopes the results, but the description does not disclose pagination, ordering, response format, or whether unpublished/draft posts are excluded. This is adequate for a simple list tool but lacks richer behavioral context.

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 sentence, 'List published blog posts.', with zero wasted words. The verb is front-loaded and the sentence is efficient, making it appropriately concise for a simple tool.

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 one-parameter list tool with no output schema and no annotations, the description states the core purpose but leaves out return-value details, ordering behavior, and usage context relative to siblings. It is minimally adequate but has clear gaps in contextual guidance.

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 input schema documents the only parameter (limit) with 100% coverage, so the schema already handles parameter semantics. The description adds no additional meaning about limit, so the baseline of 3 applies where the schema does the heavy lifting.

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 'List published blog posts.' uses a specific verb ('List') and resource ('published blog posts'), which clearly states what the tool does. It distinguishes from sibling tools by resource type (list_frameworks, list_guides, list_products) and from get_blog_post, which retrieves a single post.

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?

There is no guidance on when to use this tool versus alternatives such as get_blog_post or other list_* tools. The description does not provide context, exclusions, or explicit recommendations, leaving usage to be inferred solely from the name.

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