search_documents

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

No annotations provided, so the description carries full burden. It does not disclose whether the tool is read-only, destructive, or has rate limits. The term 'search' implies a read operation, but this is not explicit, leaving behavioral uncertainty.

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 short and front-loaded with the action. Parameter descriptions are listed clearly. It is concise without being overly terse, though it could benefit from a bit more structure (e.g., separating the purpose from parameter 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?

Despite having an output schema (therefore return values are covered), the description lacks essential context for a search tool: it does not mention that results are a list, pagination, or size limits. This could mislead an agent expecting a single document or unlimited results.

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 0%, so the description must compensate. It provides brief explanations: 'Name of the index', 'Search query', and 'Optional cluster name. Uses the default cluster if omitted.' These add basic meaning but lack detail on the query format (e.g., Elasticsearch DSL). Partial compensation for missing schema descriptions.

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' clearly states the action and resource. The name itself distinguishes it from sibling tools like 'get_document' (single retrieval) and 'delete_by_query' (destructive search), though no explicit differentiation is provided.

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 versus alternatives. The description does not indicate preferred use cases or contrast with siblings like 'get_document' or 'delete_by_query'. The agent must infer context solely from the name.

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