build_complex_query

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state whether this is a read-only operation, any side effects, required permissions, or what the output structure is. The verb 'build' is ambiguous about whether it constructs a query or executes one.

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 with no filler words. Every word contributes to the core meaning, and it is front-loaded with the primary action ('Build complex boolean queries').

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 6 optional parameters and no parameter descriptions, the one-sentence description is insufficient to guide construction of a valid query. The output schema exists but does not clarify input semantics or relationship between clauses.

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 mentions filters and aggregations but does not explain the boolean clauses (must, should, must_not) or the size parameter. The parameter names are conventional but not self-explanatory without further context.

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 builds complex boolean queries and mentions filters and aggregations, distinguishing it from simpler query tools like query_with_filters. However, it does not explicitly specify what data is being queried, relying on sibling tool context to imply the gene domain.

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?

There is no guidance on when to use this tool versus alternatives such as query_with_filters or query_genes. The description lacks context for scenario-based selection or exclusions.

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