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

With no annotations provided, the description carries the burden. It discloses the data source restriction ('Use only output by...'), how to handle missing data, and protocol support ('Only JSON-RPC 2.0 requests are supported'). It also describes the expected output format (table with categories/stories), but does not cover auth, rate limits, or error behaviors.

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 somewhat verbose and has formatting issues (missing period, malformed URL). The purpose is front-loaded, and the category explanation is relevant, but redundancy in explaining the hierarchy could be tightened.

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?

Despite the verbosity, the description provides all necessary context: what is returned, the organizational structure, presentation requirements, and data source constraints. The presence of an output schema reduces the need to describe return values, making this fairly complete. Minor gaps include no mention of sorting or error handling, but for a simple list tool this is acceptable.

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?

This tool has 0 parameters, so the baseline is 4. The description adds no parameter info, which is appropriate since the schema is empty and coverage is 100%.

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 'Returns all published articles', a specific verb and resource. It further clarifies the article organization and distinguishes itself from sibling tools that filter or search by explicitly stating it returns ALL articles.

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 explicitly states 'When you are asked to list all articles' and instructs to produce a table, giving clear context. However, it does not mention alternatives or when not to use this tool, earning a 4 rather than a 5.

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