splunk_search_history

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

No annotations are provided, so the description carries the behavioral burden. It usefully discloses that results are scoped to the current user and that it queries history/jobs, implying a read operation, but it does not clarify time-window semantics, ordering, pagination, or whether jobs include running versus completed searches.

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 and compact: one sentence states the purpose, followed by a direct explanation of the only parameter. There is no wasted text.

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 tool is simple, has an output schema, and the only parameter is explained, so the core description is adequate. However, 'recent' is undefined and there is no usage context for choosing this over related search tools, leaving a meaningful gap for an agent selecting among many siblings.

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?

The schema has 0% description coverage for the sole parameter, but the description compensates by explaining that 'count' is the maximum number of history jobs to list. The default value is available in the schema, so this is sufficient parameter semantics for a one-parameter read tool.

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-resource pair: query recent search history and jobs dispatched by the current user. It is clear what the tool returns, though it does not explicitly distinguish itself from nearby siblings such as splunk_search_status or splunk_get_search_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?

It gives no explicit when-to-use or when-not-to-use guidance and does not name an alternative sibling. The intended use is only implied by the name and the phrase 'recent search history.'

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