list_articles

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

Discloses that list_articles has no filtering parameters and the catalog can be large, indicating potential performance considerations. No annotations provided, so description carries burden; additional details like pagination could be included but not essential.

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?

Two efficient sentences with no wasted words. Purpose is front-loaded, and additional guidance is provided concisely.

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 listing tool with well-documented schema parameters and no output schema needed, the description covers purpose, usage alternatives, and limitations. Complete for intended use.

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 is 100% with clear parameter descriptions (page, per_page, sort_by, sort_order). The description adds no extra parameter-level meaning beyond the schema.

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?

Clearly states 'List Help Center (knowledge-base) articles' with specific verb and resource. Distinguishes from sibling search tool by noting lack of filtering parameters.

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?

Explicitly advises when to use search instead ('to find articles by title/body/section'), and notes that list_articles has no filtering and catalog can be large.

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