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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds real behavioral context beyond that: live research progress continues after the call, and the tool "works without UI as a structured result." Return shape and error behavior are not addressed, but the output schema covers returns.

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?

Four sentences, front-loaded with what the tool shows before the call-timing and pagination details. No filler, though the pagination and UI-less notes could be tightened slightly.

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 viewer with an output schema, the description covers purpose, call timing, pagination defaults, and headless behavior. It omits nothing critical, though it doesn't mention permission/access requirements implied by "accessible sheet."

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 must compensate, and it does: cursor/direction are described as page-navigation controls with the default (omit for first page) and sheetId is tied to the sheets_research output. The direction enum values (forward/backward) are left to the schema, a minor gap.

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 gives a specific verb ("Show") and resource ("sheet") and frames the output as an interactive table with live research progress, which separates it from plain data tools like sheets_get. It does not explicitly name a sibling it replaces, but the research-following framing makes the intent clear.

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?

It states a concrete trigger: "Call immediately after sheets_research returns its sheetId." Pagination usage is also spelled out ("omit them to start at the first page"). It lacks explicit when-not-to-use guidance versus sheets_get or sheet_workspace, so it stops short of a 5.

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