List Document Stores

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, which sufficiently convey safety. The description adds that the tool returns a list with details, but does not disclose any other behavioral traits like pagination, performance implications, or side effects. The description adds marginal value beyond 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 three sentences with a clear front-loaded purpose, followed by structured Args and Returns sections. No filler or redundant information, making it efficient for an AI agent to parse.

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 has one parameter and a presumably defined output schema. The description mentions the return format ('list with details') which is sufficient for a simple list operation. While more detail on response_format could be helpful, the output schema likely handles that. The overall completeness is good for the tool's simplicity.

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%, meaning no property descriptions exist beyond the param name. The description only states 'params: Input containing response_format' without explaining the enum values, default, or behavior. Given the low coverage, the description fails to compensate.

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 explicitly states 'List all document stores configured in Flowise' which identifies the specific verb (list) and resource (document stores). It also explains that these stores contain indexed documents for RAG, providing context that distinguishes it from other list tools like list_flows or list_assistants.

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 similar list tools (e.g., flowise_list_document_stores vs flowise_get_document_store) or under what conditions it is appropriate. No alternatives or exclusions are mentioned.

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