List Knowledge Articles

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is clear. The description adds useful behavioral context by stating that records are lightweight and omit body content, which helps set expectations about the response without contradicting the annotations.

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 extremely concise: two sentences in the first paragraph cover purpose and filters, and a final sentence directs users to the sibling tool. No word is wasted, and important information is 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 the tool's moderate complexity (8 parameters, no output schema), the description adequately explains the return scope (summaries without body), filter dimensions, and how to get full content. It lacks explicit mention of pagination behavior, but limit/offset parameters are already documented in the schema. Overall, it is sufficient for an agent to use correctly.

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?

With 100% schema description coverage, the schema already documents all 8 parameters. The description reinforces the filter options (knowledge base, category, workflow state, text search, encoded query) but does not add significant meaning beyond the schema, so a baseline of 3 is appropriate.

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 it lists knowledge article summaries from the kb_knowledge table, using the specific verb 'List' and resource. It distinguishes itself from the sibling get_kb_article by explicitly noting it returns lightweight records without body content, making the purpose unambiguous.

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?

It provides explicit usage guidance by pointing to get_kb_article when full article body content is needed, effectively stating when not to use this tool. It also enumerates common filter criteria, giving the agent clear context for when to select this tool over alternatives.

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