splunk_update_saved_search

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

No annotations are provided, so the description carries the full behavioral burden for a mutation operation. It does not disclose permissions required, whether updates are partial or replace existing values, how omitted fields are handled, or the effects of the disabled/is_scheduled flags beyond a minimal field listing.

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 purpose is front-loaded in a single sentence, followed by a compact argument list. Every sentence contributes useful information with no filler.

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 plus output schema is sufficient to identify the operation and its parameters, but for a mutation tool with no annotations it omits important context about permissions, update semantics, and side effects. It is adequate but has clear behavioral gaps.

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 0%, so the description must compensate, and it does document all six parameters with meaning beyond their titles, including optionality and the intended use of each field. The distinction between is_scheduled and disabled could be clearer, and cron/SPL formats are not specified.

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 first sentence states a specific verb and resource: update an existing saved search's settings or query. It is clear enough to distinguish this from siblings like create/delete saved search by the verb, but it does not explicitly differentiate update from related actions such as dispatch or replay.

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 implies use when modifying an existing saved search, but gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not mention sibling tools such as splunk_create_saved_search or splunk_dispatch_saved_search.

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