Fetch Slice

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

The readOnlyHint annotation is true, and the description aligns with a read-only operation ('Pull' a window). The description adds context about parameter meanings but does not go beyond the annotation to discuss side effects, permissions, or failure modes. Since annotations already cover safety, the bar is lower; the description adds some value but not rich behavioral detail.

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 two sentences long, direct, and free of unnecessary wording. It front-loads the core purpose and then gives parameter hints, making efficient use of space.

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 has an output schema (indicated in context signals), so the description need not explain return values. The description covers the primary use case and selection criteria relative to a sibling tool. It is complete enough for a simple tool, though a bit more detail on offset and job_id could have elevated it further.

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 0%, so the description is the sole source for parameter meaning. It explains path, where, and fields, but omits job_id (required) and offset (pagination). While job_id may be inferable from context, it is not explicitly described, and offset is not mentioned at all. The explanation is partial, covering 3 of 6 parameters.

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 the purpose: 'Pull one window of a job's result instead of the whole set.' It uses a specific verb ('Pull'), identifies the resource ('job's result'), and distinguishes itself from job_fetch by explicitly saying 'instead of the whole set.' No ambiguity.

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?

Explicit guidance is given: 'Use this rather than job_fetch whenever a scan produced many rows.' It also briefly explains three parameters (path, where, fields) inline, giving enough context for common use. The condition for choosing this tool over the sibling is concrete.

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