List blog posts

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

With no annotations, the description carries the full burden. It discloses that the tool is read-only, doesn't consume credits, returns paginated results, and uses a default sort of '-created_at'. This goes beyond basic operations and covers key behavioral aspects, though it doesn't mention rate limits or return structure.

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 that front-loads the core action and then packs additional relevant details (filters, sort, defaults, read-only) without any waste. Every clause provides actionable information.

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?

Given the tool's complexity (7 parameters, no required params, no output schema) and the absence of annotations, the description covers all essential aspects: pagination, filtering, sorting, defaults, and cost/read-only status. It is sufficiently complete for an agent to select and invoke the tool correctly.

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 already has 100% coverage with descriptions for all 7 parameters. The description adds valuable semantics beyond that: it explains how filters combine (status, category, tag, language), the '-' prefix convention for descending sort, and the default sort order. This helps the agent form correct queries.

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 ('List'), a specific resource ('blog posts'), and scope ('the project's'), and immediately clarifies it is paginated. It clearly differentiates itself from sibling tools like get_blog_post (singular) and list_galleries by focusing on the blog post collection.

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 provides clear context on when to use this tool: to list blog posts with optional filters and sorting. It does not explicitly name alternatives or exclusions, but the context makes it obvious that this is for multiple posts, while get_blog_post handles single posts. Slight gap: no explicit 'use this when you need a list' statement.

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