List Spreadsheet Comments

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

Annotations already declare readOnlyHint=true and destructiveHint=false, indicating safe read-only operation. The description adds no behavioral context beyond 'List all comments', such as whether replies are included, the output format, or rate limits. It relies entirely on annotations for safety signals.

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, readable sentence. It is concise but at the expense of completeness—no additional details are included that would aid understanding. It is front-loaded but lacks structure (e.g., no separation of purpose from usage).

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?

Given the tool has an output schema (not shown), the description should still provide context about what the output represents (e.g., comment IDs, threads, author info). It does not mention any filtering or sorting capabilities. The description is insufficient for an agent to fully understand the tool's behavior without inspecting the schema.

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%, and the description provides no explanation for either parameter (user_google_email, spreadsheet_id). It does not clarify their roles, expected formats, or how they constrain the results, leaving the agent without essential context beyond the schema property names.

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 it lists comments from a spreadsheet, providing a specific verb and resource. It clearly distinguishes from sibling tools like manage_spreadsheet_comment (which modifies comments) and list_document_comments (which targets documents). However, it does not specify if it lists comments across all sheets or only top-level.

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 guidance on when to use this tool versus alternatives, such as using manage_spreadsheet_comment for creating or deleting comments, or list_document_comments for other document types. The description does not mention constraints like pagination or filtering.

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