List Spreadsheet Comments

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds minimal behavioral context beyond 'list all'. It does not detail pagination, rate limits, or scope of comments (e.g., across all sheets).

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 a single, well-formed sentence that conveys the core functionality without any extraneous information. It is appropriately front-loaded and easy to parse.

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?

While an output schema exists (so return structure is defined elsewhere), the description does not outline what 'comments' includes (e.g., author, text, timestamp). It also lacks context on whether the list is limited to the user's comments or all comments on the spreadsheet, which could affect interpretation.

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%, meaning the input schema lacks parameter descriptions. The tool description does not elaborate on the purpose or format of 'user_google_email' or 'spreadsheet_id'. For instance, 'user_google_email' might be ambiguous (is it the authenticated user's email?), and this gap forces the agent to infer or hardcode.

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 action ('List'), the resource ('comments'), and the scope ('from a Google Spreadsheet'). It differentiates from sibling tools like 'manage_spreadsheet_comment' (which modifies comments) and 'list_document_comments' (which targets documents).

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?

No usage guidance is provided. There is no mention of when to use this tool versus alternatives (e.g., 'manage_spreadsheet_comment' for modifications), prerequisites, or scenarios where it should be avoided. The description is purely declarative.

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