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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds that the export is bounded and UTF-8, but it does not explain revision conflicts, error behavior, or what happens when maxBytes is exceeded.

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 direct sentences with the core operation front-loaded and no wasted wording. The larger-sheet fallback follows immediately as actionable context.

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 output schema means return values need no explanation, but the description does not cover expectedRevision, which is required for correct invocation. For a tool with three required parameters and 0% schema description coverage, this is a significant completeness gap.

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 for three required parameters. It hints at maxBytes ("bounded") and sheetId ("current sheet"), but expectedRevision is never mentioned, leaving a required concurrency parameter completely unexplained.

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 states a specific verb (Export), resource (current sheet), scope (bounded), and format (UTF-8 CSV). It also distinguishes the operation from handling larger sheets, so an agent can tell what this tool is for without opening the schema.

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 gives a clear condition and an alternative: use this for bounded current sheets, and for larger sheets query pages and assemble CSV in CodeMode. It does not name the exact sibling tool or provide any other when-not guidance, so it is helpful but not fully explicit.

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