list_ai_search_jobs

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

With no annotations provided, the description must carry the behavioral disclosure burden. It only states 'List jobs' and gives no details about pagination, return format, job states, authentication requirements, or read-only guarantees. Listing implies a safe read operation, but the description adds no explicit behavioral context beyond that.

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 with no filler. Every word contributes to identifying the operation and its target resource.

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 no output schema, no annotations, and a generic parameter schema, the one-line description is not enough. It does not explain what an 'AI Search job' is, what information the listing returns, whether pagination or filtering is available, or any operational constraints. An agent would need to infer much of the context.

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 does not add meaning beyond the schema's generic 'The account ID' and 'The instance ID' texts, and it does not explain the relationship between the two parameters or how to identify the correct instance.

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 uses a specific verb ('List') and a specific resource ('jobs for an AI Search instance'), which clearly distinguishes it from sibling tools like list_ai_search_instances, list_ai_search_items, and get_ai_search_job. Even without naming alternatives, the resource scope is unambiguous.

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 such as get_ai_search_job or list_ai_search_items. There is no mention of prerequisites, scoping, or situations where another tool should be chosen.

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