rlm_list_collections

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

With no annotations, the description discloses what types of collections are returned (owned, team, public) and the purpose, but does not detail the output structure, pagination, or any side effects. Adequate but not rich.

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?

Two sentences, front-loaded with the action, then the use case. No unnecessary words. Perfectly concise.

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 no output schema, the description explains what is returned (collection types) and the use case. It covers the essential information for a list tool, though could be improved by mentioning if pagination or sorting exists.

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 coverage is 100% and the description does not add significant meaning beyond the schema's description of include_public. Baseline 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?

Clearly states the tool lists shared context collections accessible to the user, enumerating types (owned, team, public) and specifies the use case (finding collection IDs for uploads). This distinguishes it from sibling tools like rlm_list_business_collections.

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?

Explicitly says to use for finding collection IDs for uploading documents, providing clear context. However, it does not explicitly mention when not to use it or alternatives like rlm_list_business_collections for business collections.

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