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

Annotations already cover the read-only safety profile, and the description adds substantial context on top: moderation filtering (only approved comments), the Gluecron-specific quirk that `commitId` and `side` are always null, how `isAi` is defined for gluecron[bot] notes, and auth requirements per repo visibility. These are non-obvious behaviors an agent could not infer from annotations alone.

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?

Front-loaded with the core action and scoping, and nearly every clause carries real information (thread semantics, null fields, moderation, paging). It is dense to the point of being a wall of text with deeply nested parentheticals, which slightly hurts scannability.

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?

For a 7-parameter read tool with no output schema, the description supplies the return shape (fields, thread structure, root/resolved semantics) and the paging contract, which is exactly the gap an absent output schema would otherwise leave. Nothing an agent needs to call it correctly appears missing.

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 the baseline is 3, but the description goes further by explaining what each `kind` value actually contains, that `since` operates on updated time, and that `offset` should be driven by `nextOffset`/`total` from the prior response. It omits any mention of `limit` bounds, which the schema does carry, so it is not a full 5.

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?

Opens with a specific verb and resource ("List every comment on a pull request in chronological order") and then enumerates the three comment kinds returned. This clearly separates it from the write-side siblings such as merjax_comment_pr and merjax_edit_comment without needing the schema.

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?

Gives clear conditions: use `kind` to narrow to general comments versus review comments plus summaries, `since` to filter by update time, and paging via `nextOffset`. It also states an exclusion (unsubmitted draft reviews are private and not listed) and the access model (anonymous on public, read access on private). It stops short of naming an alternative tool for, say, PR metadata or diffs, which would be needed for a 5.

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