splunk_delete_saved_search

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

With no annotations, the description carries the full burden. It usefully discloses the write-mode requirement and human confirmation, but it does not explain irreversibility, side effects, or how the confirm flag interacts with the confirmation requirement.

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 front-loaded, direct, and free of filler. The key operation and its preconditions appear in the first sentence.

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?

For a two-parameter destructive tool with no annotations but an output schema, the description covers the essential operational context: deletion, write mode, and human confirmation. It could be stronger by clarifying confirm semantics, but it is largely complete.

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 should compensate. It names both parameters ('name' and 'confirm') but gives only minimal semantics, especially for 'confirm: Confirmation flag', which does not clarify that setting it to true is what actually authorizes deletion.

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 states a specific verb and resource: 'Delete an existing saved search'. It is immediately distinguishable from sibling operations such as splunk_create_saved_search, splunk_update_saved_search, and splunk_get_saved_search.

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?

It gives clear preconditions for use: 'requires write mode and human confirmation'. It does not explicitly name alternatives or when not to use it, but the delete operation is unambiguous against its create/update/get siblings.

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