query_grid_rows

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

The readOnlyHint annotation already establishes this is a safe read, and the description adds that it returns full rows rather than a preview, plus its association with the Query Results Grid app. It omits behaviors an agent would want before calling: result expiration, row limits, pagination, or error behavior for an invalid result_id.

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?

A single compact sentence with the core information front-loaded and no filler. The trailing clause about the Query Results Grid app is the one piece of mild padding, but nothing is redundant.

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 one-parameter read tool with no output schema, the agent still lacks the return shape beyond 'full rows', any size or pagination expectations, and failure modes for missing or expired results. Coverage is adequate but leaves visible gaps.

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 0%, so the description carries the burden for result_id. Saying the rows come from 'an earlier query_grid result' does tell the agent where to obtain the id, but it gives no format, validity window, or reuse semantics.

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 names the resource (full rows) and its provenance (an earlier query_grid result), which implicitly separates it from the sibling query_grid tool that produces the result. It is a noun phrase rather than an explicit verb, but an agent can still tell what the call returns.

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?

Referring to 'an earlier query_grid result' implies the prerequisite that a query_grid call must run first and supply result_id, which is useful context. However, it never states when to prefer this over query_grid itself or what happens if the result is stale, so usage is only implied.

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