list_ai_search_items

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only states that items are listed. It fails to disclose pagination behavior, what an 'item' is, the return format, or whether any filtering is possible — all relevant for an agent predicting the call's behavior.

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?

A single sentence with zero filler, front-loaded with the verb — the description is appropriately sized for a simple listing tool with two parameters. Every word contributes meaning.

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?

The tool is simple (two required string params, fully documented schema), so the one-liner is minimally viable. However, with no output schema and no annotations, the description leaves gaps: what 'items' means in an AI Search context, whether results are paginated, and how this differs from listing instances or jobs. Adequate for basic invocation but not 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 description coverage is 100%, so account_id and instance_id are already documented in the schema. The description adds no parameter-level meaning beyond echoing the 'AI Search instance' scope, which is the baseline expected when the schema does the heavy lifting.

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 ('List') and a specific resource ('items in an AI Search instance'), making the core operation clear. However, it does not explicitly differentiate itself from closely related siblings such as list_ai_search_instances or list_ai_search_jobs, so an agent must rely on the name for disambiguation.

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 offers no guidance on when to use this tool versus alternatives. With siblings like list_ai_search_instances, list_ai_search_jobs, and get_ai_search_instance present, an agent receives no help choosing among them — e.g., no indication that instance_id must be obtained first or that 'items' means content within an instance rather than instances themselves.

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