Get Results Sample

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

Annotations already declare readOnlyHint=true, and the description adds meaningful behavioral context: it is intentionally bounded and is not meant for large retrieval. It also clarifies the purpose of the data pull (analysis), which helps the agent set expectations.

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?

Two tight sentences with no filler. The primary purpose is front-loaded, and the design rationale plus routing to the sibling tool is delivered in the second sentence.

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 read-only, bounded sample tool, the description covers purpose, scope, and the large-set alternative. The schema covers parameters and the output schema covers return shape, so nothing needed to call it correctly is missing.

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 description coverage is 100%, and the schema already fully documents url_or_hash, limit, and offset with ranges and defaults. The description's mention of 'bounded' aligns with the schema but adds no new parameter-level meaning beyond it.

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?

States a specific action ('Pull a bounded slice'), a specific resource ('a saved query's records'), and a clear intent ('into the conversation for analysis'). The phrase 'bounded slice' distinguishes it from the sibling export_results, which is designed for large sets.

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 says when to use this tool: for bounded in-context analysis. It also names the alternative for large sets ('prefer export_results') and explains why, preventing the agent from overloading context.

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