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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that: no mention of pagination behavior, default ordering, result caps, or what happens when a knowledgeBaseId does not exist — all relevant for a list tool with limit/offset.

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 short sentence with no filler, and the resource and scope are front-loaded. It is efficient, though its brevity comes at the cost of the guidance the tool actually needs.

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?

With six parameters, a fully documented schema, and read-only annotations, the definition is minimally sufficient to invoke the tool correctly. What is missing is the disambiguation from search_articles and any note on pagination/ordering, which matters for an agent choosing among 23 sibling tools.

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%, so every parameter (tags, limit, offset, status enum, category, knowledgeBaseId) is already documented in the schema. The description's 'optional filters' only gestures at the filter set and adds no semantics beyond what the schema provides, so the baseline 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 states a specific verb and resource ('List articles') plus a scope ('for a knowledge base'), so the basic action is clear. However, it is close to a restatement of the name/title and does nothing to distinguish it from the nearby sibling search_articles, which an agent could easily confuse with a filtered list.

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?

There is no guidance on when to use this versus search_articles, list_article_versions, or get_article. The phrase 'with optional filters' hints that filtering is possible but never says which situations call for this tool over the alternatives.

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