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

The annotations already declare this as a safe, read-only, non-destructive operation. The description adds useful behavioral context beyond annotations: the return shape { count, next_skip, items }, the pagination continuation pattern, and the GET /comments endpoint.

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 and front-loaded: purpose, covered entity types, return shape, pagination, single-record mode, filtering, and endpoint are all stated without filler. Each sentence carries operational 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?

Although there is no output schema, the description explains the return envelope and pagination continuation. With fully documented parameters and read-only annotations, it provides enough context for an agent to call the 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 defines every parameter. The description still adds value by explaining the relationship between next_skip and skip, the special single-record behavior of id, and the distinction between exact-match filters and MongoDB-style query.

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 states a specific verb and resource: it lists comments, scoped to tasks, files, and conversations, and names representative fields returned. It is clearly distinguishable from the sibling create_comment tool.

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?

It gives practical usage guidance: pass id to read one record, use exact-match filters or a MongoDB-style query, and use next_skip as skip for pagination. It does not explicitly state when not to use it or name alternatives, but the list-vs-create distinction is clear from the siblings.

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