splunk_search_status

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

The word 'Query' implies a read-only status lookup, and the description names the returned information (status, progress, statistics). With no annotations, however, it does not explicitly state read-only behavior, permissions, error handling for invalid SIDs, or whether polling is expected.

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 with a single useful sentence and a compact Args section. There is no filler or repetition, making it easy for an agent to parse.

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?

Because an output schema exists, the description need not explain the return structure. For a simple one-parameter status tool it covers the essential call surface, but it lacks context about obtaining the SID from an async search and when polling this status is appropriate.

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 and the only parameter is documented in the description as 'Search Job ID', which adds meaningful semantic context beyond the schema's bare 'Sid' string field. The meaning is clear, though no format or example is provided.

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: querying execution status, progress percentage, and statistics of a Search Job by SID. This is clear enough to distinguish it from result-fetching or cancellation siblings, though it does not explicitly name those alternatives.

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 says what the tool does and that a SID is required, but gives no explicit guidance on when to use it versus splunk_search_results, splunk_search_async, or splunk_search_cancel. The usage context is only weakly implied by 'Search Job by SID'.

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