advanced_query

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

No annotations provided, so the description carries the burden. It indicates it's a query tool returning results, but does not confirm read-only behavior or disclose any side effects. The example suggests a safe operation, but more detail would improve transparency.

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 structured with sections (Args, Returns, Example) and is concise. It front-loads the purpose and provides necessary details without extraneous text. Every sentence adds value.

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 0% schema coverage and no annotations, the description covers parameters adequately with an example. However, it does not detail the output schema or the allowed query types, leaving some ambiguity. Has output schema but not described; could be more complete.

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 coverage is 0%, so the description is the sole source for parameter meaning. It explains each parameter: queries (list of objects with query and type), strategy (parallel/sequential), and delay (seconds). The example clarifies usage, adding significant value beyond the schema's type-only information.

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 it is a batch query tool with complex strategies. It lists parameters and provides an example, differentiating from siblings which focus on specific analyses like gene evolution or pathway enrichment.

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?

Description mentions strategy (parallel/sequential) and delay, implying when to use each, but does not explicitly state when not to use or compare to alternatives. Sibling tools are distinct in purpose, so guidelines are somewhat implied but not explicit.

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