optimai_list_searches

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

With no annotations provided, the description carries the full transparency burden. It clearly indicates a read-only listing operation ('List recent searches made with this API key') but does not disclose additional behavioral details such as ordering of results, whether full search objects or summaries are returned, or any API-specific constraints beyond the API key scoping.

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 exactly two sentences, front-loads the core action ('List recent searches'), and uses no unnecessary words. It efficiently conveys the essential operation and the key supported filtering options.

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 description covers the core purpose, resource scope, and filtering/pagination capabilities. However, without an output schema, it does not specify the return format or ordering, and it does not explicitly distinguish itself from optimai_get_search beyond the plural vs. singular contrast. Still, for a straightforward list endpoint, the information is sufficient for selection and invocation.

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?

All five parameters are documented with descriptions in the input schema, achieving 100% coverage, so the baseline is 3. The description's summary of 'filtering by status, date range, and pagination' adds no new semantic detail beyond what the schema already provides for each parameter.

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 the specific verb 'List' with the resource 'recent searches' and scopes it to 'this API key', making the operation unambiguous. It also mentions filtering by status, date range, and pagination, which clearly distinguishes this from sibling tools like optimai_search, optimai_get_search, optimai_cancel_search, and optimai_start_search.

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 establishes a clear context for use: listing recent searches for the current API key. While it does not explicitly name alternatives (e.g., 'use optimai_get_search for a single search'), the plural 'searches' and the mention of pagination and filtering implicitly differentiate it from the single-search retrieval tool.

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