list_kvstore_collections

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

No annotations are provided, so the description carries full transparency responsibility. It explicitly states the output structure (array with fields, accelerated_fields, replicated, total count) and security constraint (results constrained by permissions). This is good disclosure for a read-only listing tool, though it could mention pagination or rate limits if applicable.

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, front-loading the action and purpose. It uses separate sentences for usage, outputs, security, and parameter, making it easy to scan. No redundant information.

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 optional parameter, no output schema), the description covers all necessary aspects: purpose, usage context, output structure, security, and parameter meaning. An agent has sufficient information to invoke this 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 one optional parameter 'app' with no description. The description adds meaning by explaining that 'app' is an optional filter for collections by app name. This compensates for the 0% schema coverage and provides clear semantics beyond the raw schema.

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 KV Store collections with basic schema details. It specifies usage for discovery of lookups, configuration, or caching, and mentions optional filtering by app. This distinguishes it from siblings like create_kvstore_collection (creation) and get_kvstore_data (data retrieval).

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 clear context for when to use the tool (discover available KV stores for specific purposes) and mentions optional app filtering. However, it does not explicitly state when not to use it or suggest alternatives such as get_kvstore_data for retrieving actual data. The guidance is adequate but lacks exclusionary advice.

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