Get all comments

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

Discloses return format (grouped, resolved as count) and implies broad fetch, but lacks details on pagination, performance impact, or maximum result handling beyond the max_threads parameter. No annotations provided.

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 sentences plus a usage note, all front-loaded with the core functionality. No redundant information.

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 the main behavior and filtering options, but lacks explanation of how filters interact (e.g., author + search), and does not detail the output structure further due to missing output schema. Still adequate for the tool's complexity.

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%, so baseline is 3. The description does not add new semantic meaning to parameters beyond what the schema already provides; usage guidance is about tool selection, not parameter details.

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 that the tool fetches every comment thread, grouped by page and canvas element, and that resolved threads are returned as a count. It also contrasts with narrower sibling tools by advising when to prefer them.

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?

Explicitly advises to use a narrower tool (unresolved/recent/mentions) or the page argument when they suffice, providing clear decision criteria for the agent.

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