list_articles

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

The description indicates a simple read operation with no side effects. For a list tool with no parameters and no annotations, it sufficiently explains the behavior. However, it omits potential details like pagination or rate limits, which may be inferred but are not explicit.

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?

A single sentence with no wasted words, front-loaded with the core action and resource. It is efficient and easy to parse.

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?

Given the tool has no parameters and an output schema exists, the description covers the essential purpose and output. It is complete for typical use, though lacking explicit mention of pagination or ordering. Still, it is adequate for a simple list operation.

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?

There are no parameters, so the description adds value by specifying the return fields (title, slug, description) beyond the empty schema. This exceeds the baseline expectation.

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 clearly states the action (list), resource (every Kettle Logic insight article), and output format (JSON), including specific fields returned (title, slug, description). It effectively distinguishes from sibling tools like get_article or search_articles by implying 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?

Usage is implied: use to get all articles. However, there is no explicit guidance on when to use this vs. sibling tools (e.g., search_articles for filtered results) or when not to use it.

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