read_comments

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

Adds pagination details and parameter clarification beyond annotations. Annotations correctly indicate read-only and open-world. No contradictions.

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 concise sentences. Front-loaded with purpose, immediately followed by pagination guidance. No wasted words.

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?

Covers pagination and item format. Lacks full return structure but annotations and simplicity of a paginated list make it sufficient.

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?

Description adds meaning for item (URL or ID) and page_token (pagination usage). With 0% schema coverage, compensates partially; page_size remains undocumented but is self-explanatory.

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?

Clearly states the verb 'List' and resource 'comments on a Doc or file'. Specifies that item can be URL or ID. No ambiguity; distinguishes from sibling tools that read document content.

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?

Explains pagination behavior (one page, use next_page_token when has_more is true). Does not explicitly state when to use this tool vs alternatives, but the unique purpose is clear.

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