list_documents

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the action and parameters, omitting details like read-only nature, default pagination behavior, or whether it returns full documents or metadata. Nothing about side effects or prerequisites is mentioned.

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 concise, with two short lines and an Args section. No fluff or repetition. It is front-loaded with the action, and the parameter explanations are efficient, although not exhaustive.

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?

The tool is simple with two optional parameters and an output schema, so the description covers the essentials: purpose and parameter meaning. However, it lacks usage context and any mention of return format or limitations, making it only minimally complete for an agent to fully understand and invoke the tool 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?

The schema has zero description coverage (0%), so the description is the only source of parameter meaning. It adds 'Optional' to collection and 'Maximum' to limit, which is helpful but minimal. It fails to clarify what a collection is or provide examples, so it only partially compensates for the schema gap.

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 documents in the knowledge base, with a specific verb and resource. It is distinct from siblings like get_document (single document) and list_collections (collections), though it does not explicitly mention alternatives or edge cases.

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 like search_documents or similar_documents. No context is given for selection or exclusions, leaving the agent to infer based solely on the name.

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