list_searches

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

With no annotations, the description must fully disclose behavior. It only says 'Retrieve saved searches' without mentioning pagination, sorting, output format, or any constraints, leaving significant gaps for a read operation.

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, succinct sentence with no wasted words. However, it could be front-loaded with more essential context without sacrificing conciseness.

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 the tool's complexity (nested QueryRequest with multiple fields) and the existence of an output schema, the description is too minimal. It fails to explain what saved searches are or how the query parameters affect results, leaving the agent underinformed.

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?

The description adds no information about the complex 'req' parameter. Although the input schema has descriptions for sub-fields, the tool description does not summarize or clarify their purpose, leaving the agent to rely solely on nested schema definitions.

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 'Retrieve saved searches.' clearly indicates the action (retrieve) and resource (saved searches), distinguishing it from sibling tools like 'search_items' which perform full-text search. However, it does not explicitly differentiate from 'search_items' or 'list_collections'.

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?

No guidance on when to use this tool versus alternatives like 'search_items' or 'create_saved_search'. The description implies use for retrieving saved searches but offers no exclusions or context.

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