list_kb_articles

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

The description identifies the operation as listing (read-only) but does not disclose behavioral traits such as default sorting, pagination behavior, or whether all articles are returned. With no annotations, the description bears full responsibility but provides only minimal insight.

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, concise sentence with no fluff. However, it may be too terse, missing opportunities to add helpful context without significantly increasing length. It is adequately front-loaded.

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 no output schema, the description should convey what the return value contains. Saying 'with their properties' is vague, and there is no mention of pagination, default behavior, or the fact that it returns a list. This is insufficient for an agent to fully understand the tool's output.

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 0%, and the description does not explain any parameter. The parameter names ('sort_by', 'order_by', 'limit', 'offset') hint at functionality but lack clarity (e.g., does 'order_by' specify a field or direction?). The description adds no value beyond the schema, which itself is sparse.

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 lists Knowledge Base articles with their properties, providing a specific verb and resource. It distinguishes from siblings like 'list_kb_articles_by_category' and 'search_kb_articles' by being a general listing, though it could be more explicit about the scope.

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 versus alternatives like 'list_kb_articles_by_category' or 'search_kb_articles'. There is no mention of context, exclusions, or prerequisites, leaving the agent to infer usage from the name alone.

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