rlm_list_business_collections

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

No annotations provided, but the description explains what the tool does (list collections for the current team), the preset inclusion, and the behavior of two parameters (include_custom and include_missing_presets), providing sufficient behavioral context.

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: first defines purpose with concrete examples, second gives usage advice. No redundant words, highly efficient.

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?

For a simple list tool with two optional parameters and no output schema, the description covers the key aspects (what is listed, when to use, parameter implications). Could specify return format, but still adequate.

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%, so baseline is 3. The description does not add extra meaning beyond the schema's parameter descriptions; it merely mentions example collections, which is not parameter-specific.

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 it lists Team Business Context collections, with specific examples like Business Response Playbook and Offer Templates, and distinguishes from sibling rlm_list_collections which lists all 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 advises 'Use this before uploading reusable business knowledge', giving a clear when-to-use scenario, though it does not contrast with alternatives like rlm_list_collections.

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