conceptio_search_batch

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

The description discloses important behavior beyond the annotations: queued execution returns an opaque job handle, polling is done via the public API or `conceptio search-job`, and sync mode returns all results in one response. It also states that each fresh subquery consumes one search credit, which aligns with the non-read-only and non-idempotent annotations.

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 front-loaded with the purpose, then efficiently covers both modes, polling, and credit cost. Every sentence adds useful information without repetition.

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 two-parameter tool with full schema coverage and annotations, the description supplies the operational details an agent needs: mode selection, return behavior, polling path, and credit implications. No output schema exists, yet the return shape for each mode is adequately described.

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 100%, so the schema already documents the sync and queries parameters. The description adds useful meaning by explaining credit usage per subquery and clarifying the queue-versus-sync limits, though it does not expand on the query object fields 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?

The description states a specific verb and resource: run multiple independent searches in one call. It clearly distinguishes the batch operation from a single search and explains both execution modes.

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?

It clearly explains when to use the default queued mode versus sync:true, including the 1–50 and 1–10 limits. It does not explicitly name conceptio_search as the alternative for single searches, but the batch context is inferable.

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