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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered without the description. The description contributes nothing beyond that — no pagination, no filtering behavior, no result shape — for a fundamentally undocumented list 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 first two sentences are a verbatim duplicate, so roughly half the text is wasted and nothing is front-loaded beyond an HTTP path. Brevity here reflects under-specification rather than efficiency.

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?

No output schema and no parameter documentation, yet the description explains neither the query semantics nor the response. For a nested-object (query/params) endpoint with zero schema coverage, the definition is not sufficient to invoke 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?

Two parameters exist (query, params) with 0% schema description coverage and no prose about either. The description does not explain what 'query' holds or which path/entity the 'params' object scopes, leaving an agent unable to supply a meaningful request without calling describe_operation first.

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 is literally the title repeated twice ("GET /api/comments. GET /api/comments."). It conveys at most that this retrieves comments, but adds no scope, filters, or distinction from close siblings such as get_comments_mentions or get_comments_field_counts.

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 when-to-use guidance, no prerequisites, and no mention of when a sibling tool would be preferable. The only routing hint ("describe_operation provides native request schemas") addresses schema discovery, not tool selection.

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