Get Search Job Results

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

With no annotations provided, the description carries the burden of explaining behavior. It discloses that the job must be completed and that pagination is driven by has_more/offset, which is useful. However, it does not mention error conditions, what happens if the job is still running, or any permissions or rate-limit considerations.

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 three short sentences with no filler. It front-loads the core purpose, then gives the exact trigger context, then tells the agent which parameters to pass. Every sentence earns its place.

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 simple paginated fetch tool with three well-documented parameters and no output schema, the description covers the essential operational context: when to call it, what it returns conceptually, and how to paginate. It could optionally describe the result payload shape, but the absence is a minor gap given the tool's 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?

Schema coverage is 100%, and each parameter already has a clear inline description. The tool description adds value by explaining the relationship between job_id and offset=next_offset, which clarifies the pagination contract beyond the raw schema.

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 clearly states a specific verb ('Fetch'), a specific resource ('results from a completed Splunk search job'), and the page-based scope. It differentiates itself from the sibling search execution tools by focusing on retrieving results rather than starting a search.

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?

The description gives explicit usage context: use after run_oneshot_search, run_splunk_search, or execute_saved_search when has_more is true. It does not explicitly mention when not to use it, but the precondition is clear and effectively excludes alternate uses.

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