List Knowledge Bases

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so safety aspects are covered. However, the description adds no additional behavioral context beyond what the annotations and parameter schema already provide. It does not mention pagination, sorting, response format, or any other operational details.

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 clearly states the action and object. It is front-loaded and free of unnecessary words. While it is minimal, it is appropriately sized for a straightforward list operation.

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 simplicity (one parameter, clear annotations, no output schema), the description is sufficiently complete. It identifies the user scope and the resource being listed. No critical information is missing for correct invocation, though it could benefit from a note about the return type or any pagination behavior.

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?

The schema description covers 100% of parameters, with user_id adequately described as 'User id whose knowledge bases to list'. The tool description does not add extra meaning beyond this; it reiterates the user scoping, so the 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 identifies the operation: 'List' with the resource 'knowledge bases' scoped to 'a user'. This distinguishes it from related tools like lyzr_kb_get (single KB) and lyzr_kb_list_documents (documents within a KB), 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?

The description provides no guidance on when to use this tool versus alternatives, such as distinguishing it from lyzr_kb_get for retrieving details of a single knowledge base or lyzr_kb_list_documents for listing documents. It simply states what it does without any exclusions or alternative suggestions.

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