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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), yet the description usefully adds that deleted comments are excluded, that visibility is role-gated, and how pagination terminates via next_cursor. It also flags untrusted-content handling, which is valuable behavioral context beyond the annotations.

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?

Four tight sentences with zero filler, front-loading what is read before the pagination rule and the untrusted-content caveat. Every sentence carries distinct load.

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 and a nested cursor object, the description adequately covers scope, deletion behavior, pagination, and security. It stops short of describing the returned comment shape or how limit interacts with paging, but it is sufficient for correct invocation.

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 only 50%, so the description carries part of the burden. It clarifies cursor pagination semantics ('next_cursor until null') and role-based visibility, but never explains the limit parameter's range or the visibility enum values, leaving gaps the schema only partially fills.

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?

States a specific verb and resource ('Read a paginated flat comment thread') and scopes it by noting it includes replies and internal notes. It distinguishes itself somewhat from the singular sibling get_feature_comment by emphasizing the 'flat thread' nature, though it never names that sibling explicitly.

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?

Provides operational guidance ('Continue with next_cursor until null') but no explicit when-to-use/when-not guidance or routing to alternatives like get_feature_comment for a single comment. Usage is implied from the resource name rather than stated.

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