rlm.docs.list

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

With no annotations, the description must disclose behavioral traits, but it only says 'List documents in session.' It does not mention what happens if the session_id is invalid, whether documents are ordered, or if pagination defaults to first page. The agent lacks critical 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?

The description is concise, with the purpose stated first followed by a bulleted parameter list. It is efficient and easy to scan, though the parameter descriptions could be more informative.

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 3 parameters and an output schema, but the description omits details like ordering, filtering, and error handling. It does not address common usage scenarios (e.g., empty session, pagination behavior). For a list tool, this lacks completeness.

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?

Parameter descriptions are minimal: 'Session to query' for session_id (redundant with schema), 'Max documents to return' for limit, and 'Pagination offset' for offset. These add some context beyond the schema types and defaults, but are very brief. Given 0% schema description coverage, the description partially compensates.

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 'List documents in session', which is a specific verb and resource. It distinguishes from sibling tools like rlm.docs.load and rlm.docs.peek by focusing on listing multiple documents. However, it does not specify the scope (e.g., all documents or filtered) beyond the session context.

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 siblings like rlm.search.query or rlm.artifact.list. No when-to-use or when-not-to-use instructions are given, leaving the agent without decision support.

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