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

Beyond the readOnly/idempotent/non-destructive annotations, the description adds substantial behavior: ordering is oldest first, replies use parentCommentId, threads are one level deep, deleted comments appear as tombstones only when a live reply exists, and mentions use a specific format. This is exactly the kind of context an agent needs to interpret results correctly.

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 front-loaded with purpose and then packs useful behavioral details about ordering, threading, tombstones, and mentions without wasting space. Every clause contributes to correct invocation or interpretation.

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 simple read-only tool with full schema coverage and no output schema, the description is largely complete: it explains the main result shape, reply threading, deleted-comment tombstones, and mention syntax. It does not mention pagination or whether all comments are always returned, which would fully close the remaining gap.

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 both entityId and entityType are already documented in the schema. The description reinforces that the thread belongs to a task or project, but adds no syntax or format details beyond what the schema already provides.

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: 'Read the comment thread on a task or a project.' It also adds ordering ('oldest first'), which clearly distinguishes this list operation from add_comment, edit_comment, and delete_comment siblings.

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?

The description gives clear usage context: it is for reading comments attached to either a task or a project. It does not explicitly name alternatives such as add_comment or edit_comment, nor does it state when not to use it, but the intended context is unambiguous.

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