documents_search

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

No annotations are available, so the description carries the full burden. It only states that it searches across all documents but does not disclose default exclusions (e.g., drafts/archived), permissions required, or output behavior. This is insufficient for a search tool with multiple filter params.

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 a single focused sentence with no redundancy, making it concise and easy to parse. However, its brevity sacrifices informational depth, but for this dimension, it earns a high score for clarity and structure.

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 the tool has 9 parameters and no output schema, the description is too thin. It fails to mention the result format, pagination behavior, or how filters like includeDrafts and includeArchived affect the search. This leaves the agent without enough context to correctly invoke the tool in complex scenarios.

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 covers all 9 parameters with descriptions, so baseline is 3. The description itself adds no parameter-specific detail; it only clarifies the overall search scope, which does not enhance understanding of individual params.

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 identifies this as a full-text search tool targeting all documents, with a specific verb (search) and resource (all documents). It distinguishes from the sibling 'documents_search_titles' by implying it searches content, not just titles.

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?

No explicit usage guidance is provided; the description does not mention alternatives like documents_search_titles or when to use this instead of documents_list. The context is only implied by the tool name and the phrase 'full-text'.

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