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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds a genuine behavioral trait the annotations do not: stable oldest-first ordering, plus the polling pattern. It says nothing about pagination behavior or result shape, so it is a modest addition rather than rich context.

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 clauses, no filler, and the resource plus ordering constraint are front-loaded before the polling hint. Every word carries information.

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 should carry more of the return shape; it conveys ordering but not whether replies are nested, flat, or include author metadata. Pagination is only indirectly implied, though the schema does document cursor as meta.next_cursor from the previous page.

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 the four parameters (limit, since, cursor, thread_id) are fully documented in the schema and the baseline is 3. 'Poll with since' adds a use-case gloss for the since parameter (incremental fetch), but no syntax or edge-case detail beyond the schema.

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 the resource precisely (a thread's replies) plus the ordering ('oldest first'), which separates it from sibling list tools like commons_threads_list and commons_conversation_get. It never uses an explicit verb like 'list' or 'fetch', but the resource and scope are unambiguous.

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?

'Poll with since' gives one concrete usage mode (incremental polling), which is useful guidance. There is no statement of when to prefer this over commons_thread_get or commons_conversation_get, and no exclusions, so it remains implied rather than explicit.

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