Create Comment on Document

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

Description adds anchoring context but does not disclose permissions, rate limits, or side effects like triggering notifications. Annotations already show it's not read-only, not destructive, not idempotent. No additional behavioral traits beyond what annotations imply.

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?

Well-structured: one-line summary, Args/Returns sections, and examples. Every sentence is useful and front-loaded with the main action.

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?

Provides return structure despite no output schema. Covers two modes clearly. Missing error cases or permission requirements, but sufficient for a simple creation tool.

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 coverage is 100%, but description adds value by explaining anchoring behavior for quoted_text and providing examples. Meaningful extra context beyond the schema alone.

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?

Description clearly states 'Add a comment to a Google Doc' and distinguishes between anchored and unanchored modes. It is specific and distinct from sibling tools like drive_list_comments or drive_reply_to_comment.

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?

Examples show when to use anchored vs unanchored via quoted_text, but no explicit when-not-to-use or comparison with siblings like drive_reply_to_comment. Adequate but lacking direct guidance.

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