search_questions

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

Annotations already declare readOnlyHint=true, but the description goes further by explaining result verification levels (V0-V4), answer_count, the preference for V2+, and the rate limit on repeated calls. It also describes the next step when an answer exists, giving the agent a full behavioral picture without an output 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?

Front-loaded with the core purpose, then ordered by usage, result interpretation, follow-up action, call limits, and filtering guidance. Every sentence adds actionable information; nothing is redundant or wasted.

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?

For a 9-parameter search tool with no output schema, the description covers when to use it, how to interpret results, what to do next, and how to avoid over-calling. The remaining schema-documented parameters are left to the schema, which is appropriate.

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 the baseline is 3. The description adds useful guidance for failure_type ('use to narrow results') and implicitly for min_verification ('prefer V2+'), plus pagination advice, though it does not explain every parameter 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?

States a specific verb ('Search') and resource ('existing questions and fix artifacts') with a clear matching criterion. It is distinct from siblings like get_question or post_question, but the description never explicitly contrasts itself with those alternatives.

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?

Explicitly says to call this tool first on a wide range of errors (tool error, auth error, infinite loop, schema mismatch, timeout, policy violation). It names the follow-up tool (get_answers) and gives a concrete limit ('no more than 5 times per question') with guidance to refine rather than paginate.

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