Get Search Job Results

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

No annotations are present, so the description carries the burden of behavioral disclosure. It does state that the job must be 'completed' and that this returns 'one page', which is important context. However, it does not mention what happens if the job is still running, has expired, or if the sid is invalid, nor does it describe the response shape. This is adequate but not rich.

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?

Three concise sentences each earn their place: the first states what it does, the second states when to use it, and the third states how to pass parameters. No filler or redundant restatement of the schema.

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 paginated fetch tool with three simple parameters and no output schema, the description covers purpose, prerequisites, and pagination mechanics. It implies the response contains has_more and next_offset, which is enough for correct invocation. Missing details like error behavior for expired jobs are minor given the simplicity.

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 input schema already covers 100% of parameter descriptions, giving a baseline of 3. The description adds actionable guidance beyond the schema: 'offset=next_offset' tells the agent to set offset from the previous response's next_offset field. This relationship is not in the schema and materially improves correct usage.

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 the verb 'Fetch' and resource 'one page of results from a completed Splunk search job'. It clearly distinguishes from siblings like get_search_job_info (job metadata) and run_oneshot_search/run_splunk_search/execute_saved_search (search initiation) by narrowing to paginated result retrieval from an already-completed job.

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?

Explicitly specifies when to use: 'after run_oneshot_search, run_splunk_search, or execute_saved_search when has_more is true'. It also gives a concrete usage pattern: 'Pass job_id and offset=next_offset'. This tells the agent the prerequisite and pagination workflow with no ambiguity.

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