list_change_comments

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

With no annotations, the description carries full burden but reveals no behavioral traits: no mention of read-only nature, return format, pagination, authentication, or whether draft comments are included. The phrase 'responding to comments' could mislead an agent into thinking the tool can post responses, which is likely not the case.

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 compact at one sentence, but the list of use cases is somewhat redundant (reviewing feedback, reading comments, analyzing comments) and lacks a clear structure. It is not overly verbose, but it could be more direct.

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?

Given that there is no output schema and no annotations, the description should provide more context about return values, scope of comments, and relationship to sibling tools. It does not, leaving significant gaps for an agent to safely invoke and interpret results.

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 0%, and the description provides no explanation of change_id or gerrit_base_url. Property names are self-explanatory at a basic level, but the description does not clarify formats, defaults, or optionality beyond the schema, so it adds no value.

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 says the tool is 'useful for reviewing feedback, reading comments on a change, analyzing comments, and responding to comments,' which implies listing/reading comments but does not explicitly state 'lists comments for a change.' It lacks a specific verb+resource statement and does not differentiate from sibling tools like list_draft_comments.

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?

No mention of when to use this tool versus alternatives. It vaguely implies usage for reviewing comments but does not indicate that draft comments should be handled by list_draft_comments or that get_change_details might include comment summaries. No exclusions or alternatives are provided.

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