outline_list_documents

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to mention critical traits: whether the operation is read-only (implied but not explicit), what data structure is returned, pagination behavior beyond the limit parameter, or any rate limiting concerns.

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 single-sentence description is extremely compact with no redundant words, front-loading the action 'List documents'. However, given the presence of sibling tools with similar purposes, the brevity may be excessive as it sacrifices necessary differentiation guidance.

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 description is inadequate given the tool ecosystem: it lacks an output schema and fails to explain the distinction between 'list' and 'search' functionality, which is critical for correct agent selection. For a tool with zero required parameters and multiple document-related siblings, more contextual guidance is needed.

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?

Input schema has 100% description coverage with clear documentation for both 'collectionId' and 'limit' parameters. The description mentions filtering by collection, aligning with the schema, but adds no additional semantic context (e.g., explaining Outline's collection hierarchy) beyond what the schema already provides. Baseline 3 is appropriate given complete schema coverage.

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 verb 'List' and resource 'documents from Outline', establishing the core function. However, it does not explicitly differentiate from the sibling tool 'outline_search_documents', leaving ambiguity about when to use listing versus searching.

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 phrase 'optionally filtered by collection' provides implied usage context for when filtering is needed. However, it lacks explicit guidance on when to prefer this tool over 'outline_search_documents' or 'outline_get_document', and states no prerequisites or exclusions.

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