List Knowledge Base Entries

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds 'with optional filtering and pagination' which is already implied by the schema. No additional behavioral context is provided beyond 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 a single concise sentence that front-loads the purpose. It wastes no words, but could include a bit more context about return format or specific filtering options.

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 no output schema, the description should describe what the tool returns (e.g., list of entries with metadata, pagination info). It also lacks any usage context among many similar list tools. The description is too minimal for a 5-parameter tool.

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 baseline is 3. The description adds 'optional filtering and pagination' but does not further explain any parameter beyond what the schema already provides (each param has a description).

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 retrieves entries from a knowledge base with optional filtering and pagination. This is a specific verb-resource combination that distinguishes it from sibling tools like get_knowledge_base (gets KB itself) or list_knowledge_bases (lists KBs).

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?

The description implies usage (to list entries within a specific KB), but provides no explicit guidance on when to use vs alternatives like list_knowledge_bases or search_knowledge. Given the large number of sibling list tools, explicit exclusions would help.

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