query_documents

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

No annotations provided, but the description explains both keyword and semantic search, and that results include a relevance score (0 = most relevant). This transparently describes behavior beyond the schema.

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?

Three sentences with no unnecessary information. Each sentence earns its place by providing distinct, useful 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?

Given the low complexity (2 parameters, no output schema), the description fully covers purpose, behavior, and usage. The mention of scoring is especially helpful.

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 coverage is 100%, and the description adds value by explaining that query words are matched exactly and semantically. For limit, it includes recommendations (5 for precision, 10 for balance, 20 for exploration) that go beyond the schema.

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 'Search ingested documents,' using a specific verb and resource. It distinguishes itself from sibling tools (e.g., delete_file, ingest_data) as the only search tool.

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?

Provides guidance on preserving user terms and adding context for ambiguous queries. Does not explicitly state when not to use, but given no alternative search tools, this is sufficient.

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