list_blog_posts

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

With no annotations, the description must fully disclose behavior. It states the tool lists recent posts, implying a read-only operation, but does not disclose that the default status is 'all' (including drafts) or that the default limit is 10. This omission could mislead an agent expecting only published posts, creating a transparency gap.

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, clear sentence in Spanish, front-loaded with the action and resource. It is concise, contains no unnecessary words, and is appropriately structured for quick comprehension.

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?

The tool is a simple list operation with optional parameters, and the schema provides defaults for limit and status. The description conveys the core purpose, and the schema fills in parameter details. Although it lacks an explicit return format, 'list' implies a collection of blog posts, making it sufficiently complete for the context.

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%. The description does not mention the 'limit' or 'status' parameters at all, leaving their meaning entirely to the schema. Since the description must compensate for low coverage and does not, it adds no value beyond the schema for parameter 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?

The description clearly states the tool lists recent blog posts using the specific verb 'Lista' and resource 'artículos de blog'. It distinguishes from siblings like publish_blog_post (write operation) and get_blog_post (singular retrieval), making the purpose unambiguous.

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?

No explicit when-to-use or alternative guidance is provided. The description implies usage because it names the resource and action, but it does not explicitly state when to use this tool versus list_pois or get_blog_post. Usage is inferred rather than directly instructed.

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