search_documents

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

The description goes beyond annotations by disclosing that the default mode stays local and offline, while enhanced mode may send bounded query and candidate content through a separate transport. This is valuable behavioral transparency not covered by readOnlyHint or destructiveHint.

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—two sentences that cover the core action, the resource, and mode-specific behavior. No redundant words or unnecessary details.

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?

There is no output schema, and the description does not mention what the search returns (e.g., matches, excerpts, or metadata). While the mention of 'candidate content' hints at output, the lack of explicit return information is a gap.

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 50% (three out of six parameters have descriptions). The tool description does not add any additional parameter details, so the baseline score of 3 applies. It neither clarifies nor obscures the parameters.

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 tool's purpose: 'Search one verified snapshot.' It specifies the resource (snapshot) and the action (search), and briefly explains the two modes. This distinguishes it from sibling tools that retrieve metadata or excerpts.

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 mentions when the default vs enhanced mode is used, but does not explicitly state when to choose this tool over alternatives like find_in_document or get_excerpt. The guidance is implied rather than explicit, leaving some ambiguity about selection context.

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