splunk_get_search_performance

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

No annotations are provided, so the description must carry the behavioral load; "Inspect" implies a read but this is inference, not disclosure. It says nothing about required permissions, result size/limits, or which search-head components are covered, though the output schema partially relieves the need to describe return values.

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 sentence plus a compact Args block; the purpose is front-loaded and nothing is padded. Minor awkwardness from the empty title and lone-arg Args formatting.

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 one-parameter read tool with an output schema, the basics are covered. Missing is any statement of scope (per-search-head vs cluster-wide) or the conditions under which the tool returns sparse data, which an operator troubleshooting performance would need.

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%, but the description compensates for the single parameter by explaining earliest_time as the "Search audit window" and restating the '-4h' default. It adds meaning, but not accepted time syntaxes or behavior when the window exceeds retention.

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?

States a specific verb ("Inspect") and resource ("search head performance, execution times, and resource utilization"), so the agent knows this is a read-only performance inspection. It does not distinguish itself from nearby siblings like splunk_detect_slow_searches, splunk_get_search_concurrency, or splunk_diagnose_performance.

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 guidance on when to use this tool versus the several performance-related siblings, and no stated prerequisites or exclusions. The only usage hint is the default time window.

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