List Saved Searches

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

With no annotations provided, the description carries the burden of behavioral disclosure. It adds meaningful context: results include ownership, schedule, visibility, and permission metadata, and results are limited to saved searches the current user can access. It does not mention pagination, ordering, or output shape, but for a list tool this is reasonably transparent.

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 three sentences and immediately states the core purpose. Every sentence adds value: what is listed, how to use it, and the access limitation. No filler or redundancy.

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 a straightforward list operation with four optional well-documented parameters and no output schema. The description covers purpose, filters, metadata returned, and access scope, which is sufficient for an agent to select and invoke it correctly. Some minor gaps remain around pagination and exact return formatting, but they are not critical.

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 the input schema already explains all four parameters. The description mostly restates filtering by owner/app/sharing, which adds little beyond the schema. The baseline of 3 applies because the structured fields carry the semantic weight.

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 a specific verb ('List') with a clear resource ('saved searches') and enriches it with metadata types (ownership, schedule, visibility, permission). It distinguishes itself from siblings like get_saved_search_details or run_splunk_search by focusing on discovery and filtering of saved searches.

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?

Explicitly states when to use the tool: 'Use this to discover available reports/automations and to filter by owner/app/sharing.' It also communicates an access boundary, but does not name alternative tools for different use cases (e.g., get_saved_search_details for a single saved search).

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