execute_saved_search

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

With no annotations, the description carries full burden. It discloses that results are capped by max_results, mode used, timing, and job id if job mode. It also mentions security constraints ('execution and results are constrained by the authenticated user's permissions'). This adds good behavioral context.

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?

Description is two short paragraphs, front-loaded with the core purpose. Each sentence adds value. No redundant or vague statements. Slightly more detail could be added without harming conciseness, but overall efficient.

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 7 parameters, no output schema, and no annotations, the description covers essential usage and output but lacks parameter-specific guidance and does not explain what a saved search is. It also misses comparison to similar execution tools. Adequate but not fully comprehensive.

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 description must compensate. It explains the 'mode' parameter (oneshot vs job) and implies max_results via output description. However, it does not clarify 'name' (must match an existing saved search), time formats for earliest_time/latest_time, or the purpose of 'app' and 'owner' parameters. Partial but not comprehensive.

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 action ('Run a saved search by name') and the resource, with specific verb 'execute'. It distinguishes from sibling tools that create, delete, or list saved searches, and mentions optional time overrides and mode selection.

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 advises using this tool to 'execute existing reports/automations quickly' and explains the two modes (oneshot vs job). However, it does not differentiate from siblings like 'run_oneshot_search' or 'run_splunk_search', leaving ambiguity about when to prefer this tool over those.

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