List news articles

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

The readOnlyHint annotation already establishes the safety profile, lowering the burden. The description adds useful behavioral context by indicating the operation is paginated, which goes beyond the annotation. However, it stops short of additional behavioral traits like default page size or behavior of the all parameter, though those are captured in the input schema.

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 exactly one concise sentence with a leading verb and resource name. It is front-loaded with the core action and provides the key pagination qualifier without any filler or redundant information.

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 read-only list tool with no required parameters and fully documented parameters, the description correctly conveys the operation and its paging characteristic. While there is no output schema and the description does not detail the exact return attributes, the store-specific 'news articles' phrase provides enough context for an agent to understand what the tool returns without needing deeper documentation.

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 100%, with each parameter (all, page, per_page) already well documented in the input schema. The description's paginated mention loosely relates to these parameters but adds no new semantic detail beyond what the schema already supplies, so the baseline score of 3 applies.

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 'store news articles' and notes pagination. This clearly distinguishes it from sibling tools like get_blog, create_blog, and update_blog, which serve different purposes.

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 word 'List' implies this is the tool for enumerating multiple news articles rather than fetching a single one, providing some context. However, the description offers no explicit guidance on when to choose this tool over alternatives such as get_blog, nor does it mention exclusion criteria.

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