search_list

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

With no annotations, the description carries the full burden. It discloses important behaviors: results are summaries, sorted newest first, limit defaults to 25 and hard-capped at 100. It doesn't mention pagination or error handling, but the described behavior is sufficient for basic usage.

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 compact, well-structured docstring with a clear summary line followed by a parameter list. Every sentence is informative, no fluff, and the key behavior (newest first, default limit, cap) is front-loaded.

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 has no output schema and no annotations, so the description must cover return behavior. It states 'matching message summaries' and ordering, which is mostly adequate, though it could mention whether summaries contain message IDs or how to fetch full messages. Still, given the presence of sibling get_message, this is a minor gap.

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 0%, so the description must fully explain parameters. It does so excellently: each parameter has a clear semantic ('substring to match', 'free-text across whole message', 'ISO date'), plus helpfully documents defaults and limits that aren't in 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 clearly states the tool searches a mailing list and returns matching message summaries, with an explicit ordering (newest first). This is a specific verb+resource combination that distinguishes it from sibling tools like list_mailing_lists, page_list, and get_message.

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 clear context: it's for searching across messages in a mailing list with various filters. It doesn't explicitly state when to prefer this over alternatives, but the purpose is unambiguous from the name and description, giving the agent enough guidance to choose it appropriately.

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