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

Annotations already establish readOnly/idempotent/non-destructive safety, so the bar is lower; the description still adds real behavioral context beyond that: newest-first ordering, the 30-minute-after-post freshness rule, and the sentiment/intent enrichment plus mentionId backlink. It does not cover pagination behavior, but this is a solid addition over 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?

Two information-dense sentences with no filler, and the core resource-and-ordering fact is front-loaded. The second sentence is slightly run-on, packing availability timing and keyword conditions together, but every clause earns its place.

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, the description carries the return-value burden and largely meets it by describing ordering, enrichment fields, and the mentionId backlink. Divided coverage of pagination and error behavior is the only notable gap for a three-parameter list tool.

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%, with id, limit, and cursor all documented in the schema, so the baseline is 3. The description adds no parameter-level detail (e.g. what mentionId values look like or how cursor chains), leaving the schema to do all the work.

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 names a specific resource (the comments under a mention's post) and states ordering (newest first), which tells an agent exactly what it retrieves. However it is framed as a description of returned content rather than a crisp verb+resource statement, and it never contrasts itself with siblings like get_mention or search_mentions.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The 'Filled for new relevant mentions of keywords with comments on' clause hints at an availability precondition but does not tell the agent when to reach for this tool versus other mention tools.

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