Search Api Index List

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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: no statement that this is a read-only, non-destructive enumeration, no pagination behavior despite page_limit/page_offset being present, and no filtering semantics for the filters/server_id params. It is not misleading, but it is effectively behaviorally silent.

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 single sentence is front-loaded and waste-free, which satisfies conciseness. But at this length it reads as under-specification rather than efficiency, since nothing of substance is conveyed beyond restating the tool name.

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?

An output schema exists, so return values need not be explained, and there are no required parameters. Still, for a paginated, filterable list tool the description omits the pagination and filtering contract entirely, leaving the agent unable to call it correctly without inspecting the raw schema.

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 0% across four parameters, and the description compensates for none of it. It never explains what filters accepts, what server_id scopes, or how page_limit/page_offset paginate, so an agent has no semantic anchor for any argument.

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 clear verb+resource pair ("List" + "Search API indexes"), which is enough to separate it from search_api_index_get/create/update. However, it gives no scope detail (e.g. all indexes across servers vs. a single server) and never names a sibling, so the agent must infer the boundaries of the resource.

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?

There is no when-to-use guidance at all. The description does not say when to call this instead of search_api_index_get, nor does it mention prerequisites such as a configured server. Any routing decision is left entirely to inference from the tool name.

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