strapi_list_blog_posts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions 'advanced filtering, sorting, and pagination,' which hints at read-only, non-destructive behavior, but doesn't explicitly state this is a safe read operation, describe potential rate limits, authentication needs, or what the return format looks like (e.g., array of posts). For a tool with 8 parameters and no annotations, this leaves significant gaps in understanding its behavior.

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, efficient sentence that front-loads the core purpose ('List all blog posts') and adds key features ('with advanced filtering, sorting, and pagination') without waste. Every word earns its place, making it easy to scan and understand quickly.

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 (8 parameters, no output schema, no annotations), the description is adequate but incomplete. It covers the basic purpose and hints at functionality, but lacks details on behavioral traits (e.g., read-only nature, response format) and doesn't compensate for the missing output schema. For a list tool with filtering, more context on usage and results would be helpful, though the high schema coverage mitigates some gaps.

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 100%, so the schema already documents all 8 parameters with descriptions, defaults, and enums. The description adds minimal value beyond the schema by mentioning 'advanced filtering, sorting, and pagination,' which aligns with parameters like 'status', 'sort', 'page', and 'pageSize', but doesn't provide additional syntax, format details, or usage examples. Baseline 3 is appropriate as 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 clearly states the action ('List all blog posts') and resource ('blog posts'), which is specific and unambiguous. It distinguishes from sibling tools like 'strapi_get_blog_post' by indicating it returns multiple items rather than a single one. However, it doesn't explicitly differentiate from other list tools like 'strapi_list_events' or 'strapi_list_tutorials' beyond the resource name.

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 retrieving multiple blog posts with filtering capabilities, suggesting it's for browsing or searching rather than fetching a single post. However, it lacks explicit guidance on when to use this versus alternatives like 'strapi_get_blog_post' (for single posts) or other list tools for different resources, and doesn't mention prerequisites or exclusions.

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