splunk_detect_slow_searches

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

No annotations are provided, so the description carries the full burden. It doesn't say what data source is queried (job history vs. search endpoint), whether it requires admin permissions, or what 'expensive' is measured by beyond duration. Only the read-only nature is implied by 'Identify'.

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?

One summary sentence plus a short args list; front-loaded and free of padding. The Args block is functional, though terse enough that some entries read as labels rather than explanations.

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?

An output schema exists, so return values needn't be explained. But for a diagnostics tool with zero annotations and 0% schema coverage, the description should at least clarify the time-format convention and the notion of 'expensive' — those gaps remain.

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 does compensate by explaining all three parameters. However 'earliest_time: Search window' gives no format hint (the schema default '-24h@h' is unexplained) and 'count' is described only as 'Maximum slow searches to list', so the compensation is partial.

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?

Clear specific verb+resource: identifies slow/expensive searches above a duration threshold. This distinguishes it reasonably from siblings like splunk_get_search_performance or splunk_search_history, though it never names those alternatives explicitly.

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 statement of when to use this versus splunk_get_search_performance, splunk_get_search_concurrency, or splunk_search_history, all of which overlap in the 'search cost/perf' space. The agent must infer the choice from names alone.

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