acedatacloud_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 one meaningful behavioral trait – this is a public endpoint requiring no account or blog permission – which is genuinely useful. But it omits pagination behavior, default ordering, whether unpublished/draft content is included, and how the lang translation parameter affects results.

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?

Two short sentences, front-loading the scope statement before the access note. Nothing is wasted, though the terseness comes at the cost of the missing parameter guidance noted elsewhere.

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?

An output schema exists so return values need not be explained, but for a five-parameter, zero-required listing tool with low schema coverage, the description leaves the agent guessing about pagination, category filtering, and translation behavior. It is under-specified for the tool's complexity.

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 only 20%, so the description must compensate and does not. 'articles or videos' loosely maps to content_type, but lang, limit, offset, and category filtering/pagination semantics are never mentioned, leaving four of five parameters with no descriptive support beyond bare schema fields.

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?

States a specific verb+resource ('List published articles or videos'), which clearly separates it from the get_blog_post sibling that fetches a single post. It does not distinguish itself from other list-style siblings such as list_showcases or list_announcements, so it stops short of a 5.

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 account or blog permission required' gives one useful usage condition (public, auth-free access), which is real guidance. However, there is no explicit when-to-use vs get_blog_post, no mention of when to prefer list_blog_posts over sibling list tools, and no exclusions.

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