outline_search_documents

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

No annotations are provided, and the description discloses no behavioral traits beyond the basic action. It fails to indicate whether the search covers document titles, body content, or both; how results are ranked; or whether the operation is read-only versus generating server load.

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 consists of a single, efficient sentence with no redundant words or tautology. However, given the lack of annotations and output schema, it may be overly terse, sacrificing necessary behavioral context for extreme brevity.

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?

With no output schema and no annotations, the description should explain the search scope (titles vs. content), result format, or pagination behavior. It provides none of this context, leaving significant uncertainty about what the tool returns and how it behaves.

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 input schema has 100% description coverage for both parameters (query and limit), clearly documenting their purpose and default values. The description adds no additional semantic information beyond what the schema already provides, meeting the baseline for high-coverage schemas.

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 'Search for documents in Outline' provides a clear verb (search) and resource (documents in Outline). However, it fails to distinguish this tool from sibling `outline_list_documents`, which also retrieves documents but likely without full-text search capabilities.

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 offers no guidance on when to use this tool versus alternatives like `outline_list_documents` or `outline_get_document`. It does not clarify that this tool is intended for full-text search queries rather than browsing or direct document retrieval.

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