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

With no annotations provided, the description carries the full burden. It does disclose that the tool lists all articles and what fields are returned, indicating a read-only, broadly scoped operation. However, it omits details about pagination, ordering, or potential error conditions, which are useful for a full behavioral picture.

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, front-loaded sentence with no redundancy. Every word contributes to the tool's purpose and output characteristics.

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?

For a simple list tool with one optional parameter and no output schema, the description covers the returned fields adequately. However, it lacks guidance on how it differs from search_articles and get_article, and does not mention potential behavioral caveats like pagination, making it only minimally complete.

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 coverage for the single 'tag' parameter is 100%, and the description adds no extra meaning beyond the schema. The baseline of 3 applies because the schema already adequately documents the parameter.

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 uses a specific verb 'List' with a clear resource 'all blog articles' and enumerates the returned fields (slug, title, description, date, tags, reading time). The explicit 'all' distinguishes it from siblings get_article (single article) and search_articles (search behavior).

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 use when you want all articles, but it does not explicitly state when to prefer this over search_articles or get_article, nor does it mention any exclusions or preconditions. The guidance is only implied by the word 'all'.

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