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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, not open-world), so the bar is lower. The description still adds real operational context: ordering is newest first, records are retained only 30 days, and each row includes the comment, sentiment, moderation action, AI draft, and reply outcome. It does not describe pagination behavior beyond the schema's cursor, but that gap is minor.

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 short sentences, front-loaded with the identity of the resource, then retention and ordering, then the payload, then the most important filter hint. No sentence is redundant with the schema.

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 read-only listing endpoint with six fully documented optional parameters and no output schema, the description supplies the missing return-shape information and retention constraint. Only the pagination/next_cursor follow-through is left implicit, which keeps it from a full 5.

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 would be 3. The description earns above baseline by explaining what the status filter means in workflow terms ('pending is the approval queue'), giving the enum a purpose the schema alone does not convey.

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 first sentence names a specific verb and resource ('List handled comments') and the second narrows scope to comments processed by the AI Comment Manager, which distinguishes it from siblings like get_handled_comment and list_comment_triggers. It stops short of naming those siblings explicitly, so differentiation relies on inference.

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?

'status=pending is the approval queue' implicitly routes the agent toward approve/reject comment reply tools, which is genuinely useful. However, there is no explicit when-to-use versus when-to-use-get_handled_comment guidance and no statement about what this tool cannot do.

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