Build Search Query

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'Build a structured search query' without specifying whether this is a pure computation, makes network calls, returns data, or has side effects. This lack of context is a significant gap for an agent.

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, front-loaded sentence of 11 words with no redundancy or filler. Every word contributes to the core meaning, making it appropriately concise for the information conveyed.

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?

With 5 parameters including a nested dateRange object and no output schema, the one-sentence description is insufficient. It fails to describe what the resulting query looks like, how it integrates with other search tools, or any constraints on filters, leaving significant contextual gaps.

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?

The input schema already provides exhaustive descriptions for all 5 parameters (100% coverage), so the baseline is 3. The description's mention of 'filters' adds no extra semantic value beyond the schema, and no additional formatting or relationship details are given.

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 action ('Build') and the resource ('a structured search query for AP content using filters'), making it evident this is a query constructor rather than a search executor. However, it does not explicitly differentiate itself from sibling tools like optimize_search_query or search_content, which slightly limits the score.

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 provides no guidance on when to use this tool versus alternatives. There are no 'use when' statements, exclusions, or mentions of sibling tools, leaving usage entirely to inference.

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