list_articles

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'get a list' which is inherently read-only but provides no information about pagination, sorting, filtering parameters, or what fields are returned. It does not reveal any side effects or caveats.

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 sentence, which is very concise, but it essentially restates the tool name. It conveys no additional information beyond the resource being listed, and it could be more informative without losing conciseness.

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 tool with 9 parameters, no output schema, and no annotations, this description is severely inadequate. It leaves all behavioral aspects—filtering, pagination, default page size, response format—to the imagination. The description does not meet the burden for a non-trivial 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?

Schema description coverage is only 11%, meaning 8 of 9 parameters are undocumented. The description adds nothing about the parameters—it doesn't explain what 'name', 'slug', 'search', etc. do. The only documented parameter (updated_at) has a schema description, but the description doesn't even acknowledge the parameters. This is a significant gap.

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 tool's function: fetching a list of Knowledge Base Articles. It uses a specific verb ('get') and resource, and is distinct from sibling tools like get_article (single article). However, it lacks any detail about the scope or filtering behavior, so it's clear but minimal.

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?

No guidance on when to use this tool vs alternatives such as get_article. It does not mention any prerequisites, pagination, or whether it supports filtering. The description implies a simple list operation but gives no context for selection.

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