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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds substantial additional behavior: chronological ordering, the three kinds, thread root and resolved-state semantics, always-null commitId and side, approval/draft visibility rules, paging via total and nextOffset, and anonymous versus authenticated access. This is well beyond what the annotations provide.

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 long but dense and front-loaded: the first sentence states the core action and return categories. Subsequent sentences earn their place by covering thread semantics, null fields, visibility rules, paging, and auth. Minor length is justified by the tool's complexity.

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?

With no output schema, the description effectively supplies the missing return-value context: comment categories, author fields, timestamps, thread structure, null fields, paging totals, and access behavior. An agent has enough information to call and interpret this tool correctly.

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 100%, so the schema already documents owner, repo, number, kind, limit, since, and offset. The description reinforces kind and since semantics and explains how nextOffset pages through results, but it does not add materially new parameter constraints beyond the schema, so the baseline of 3 applies.

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 opens with a specific verb and resource: "List every comment on a pull request in chronological order," and immediately specifies the three comment kinds. This distinguishes it from write-oriented siblings like gluecron_comment_pr and from PR-level tools like gluecron_get_pr.

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?

Usage context is clear: it explains filtering by kind and since, what is included (approved comments only), and what is excluded (unsubmitted draft reviews). It also states access requirements for public versus private repos. However, it does not explicitly name sibling alternatives or state when another tool should be preferred.

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