Documents: Search

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description adds no extra behavioral context. It does not mention pagination, parameter-dependency, or any side effects. The description merely restates the tool's purpose without revealing behavioral traits.

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 sentence, concise and well-structured with no wasted words. It is appropriately front-loaded but could be slightly more informative without losing conciseness.

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 5 parameters and no output schema, the description is insufficient. It does not explain return value format (e.g., list of document IDs vs full objects), pagination behavior, or relationship to sibling tools. More context is needed for an AI agent to fully understand the tool's capabilities.

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 description coverage is 100% with all parameters documented. The description 'Search for documents' adds no additional meaning beyond what the schema provides. Baseline of 3 is appropriate as schema already explains parameters well.

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?

Description 'Search for documents' uses a specific verb ('search') and resource ('documents'), clearly indicating it's a search operation. It distinguishes from sibling tools like 'documents-list' and 'documents-get-by-id' by implying filtering. However, it does not explicitly state the search scope (e.g., by title) or differentiate from 'documents-list'.

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 guidance on when to use this tool over alternatives. The description does not specify when to prefer 'documents-search' over 'documents-list' or other search tools. No exclusionary criteria or context provided.

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