create_search_query

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

No annotations are provided, so the description carries the burden. 'Save' indicates a mutating operation, and the note about the sql field being an Elasticsearch SQL WHERE clause adds useful context. However, it doesn't disclose return values, validation behavior, or side effects, leaving gaps typical of a create operation.

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 two sentences long, front-loads the primary action ('Save a new search query'), and includes only the essential constraint about the sql field. No wasted words or redundancy.

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's simplicity (3 params, 100% schema coverage, no output schema), the description adequately covers the core action and the most critical parameter constraint. It doesn't mention output or prerequisites, but these are less critical for this straightforward create operation.

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%, so baseline is 3. The description adds a mild prescriptive nuance ('should contain') to the sql parameter, but this largely echoes the schema's own description. No significant added meaning beyond what the schema already provides.

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 'Save a new search query' with a specific verb (save) and resource (search query), distinguishing it from sibling operations like list, get, update, and delete. The word 'new' reinforces the create intent.

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 word 'new' implies this tool is for creating a search query, but there is no explicit guidance on when to use it vs. alternatives like update_search_query for modifying existing queries. Usage is implied rather than directly stated.

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