list_blogs

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

With no annotations provided, the description carries the burden of disclosing behavior. It reveals a non-obvious fact: even detail='full' omits article bodies to keep responses bounded. It also clarifies that `limit` controls row count, not `detail`. This adds valuable behavioral context beyond the schema, though it doesn't describe the response structure or error conditions.

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 three sentences, front-loaded with 'LIST tool' to immediately set context. Every sentence provides meaningful guidance with no redundancy or filler.

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 description covers the core purpose, the key behavioral nuance (body omission), and the critical parameter interaction. It doesn't explicitly state the return type (e.g., array of blog objects), but for a read-only list tool with a well-specified schema, this is a minor gap.

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 schema lacks a description for `limit`, but the tool description fully explains its default, max, and its relationship with `detail`, preventing misuse. It also clarifies that `detail` controls verbosity, not row count, which is not immediately obvious from the enum alone.

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 opens with 'LIST tool' and clearly indicates the tool lists blogs (blog articles). It distinguishes itself from the sibling tool get_blog_article by explicitly stating that article bodies are omitted and directing the user to call get_blog_article for content.

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?

It provides explicit guidance on when to use this tool vs. reading article content, naming get_blog_article as the alternative. It also explains how to get a 'full list' of titles by raising `limit` and keeping `detail='short'`, giving clear usage direction.

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