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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds a genuinely non-derivable behavior: the response exposes a next_cursor that must be fed back in as cursor, which is the key to not missing pages given there is no output schema. It still says nothing about ordering or default page size.

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 sentences, front-loaded purpose first, then the operational pagination hint — no filler. Minor friction: it references a response field name (next_cursor) that is not documented anywhere else, which reads slightly awkwardly against the schema's 'cursor'.

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 3-parameter, zero-coverage schema with no output schema, the description should explain the limit range/default and the topic filter to make the tool callable with confidence. Instead only pagination is covered, leaving two of three parameters opaque.

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 0%, so the description carries the full burden for limit, topic and cursor, yet it only maps next_cursor to cursor. The 1-50 bound on limit, the absence of a stated default, and the matching semantics of topic (exact vs partial, case sensitivity) are undocumented in both places.

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 ("List public questions") with a scope qualifier (public), which lets an agent distinguish it from get_thread (single item) and list_replies (replies). It stops short of naming siblings explicitly or clarifying what 'public' excludes.

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?

Usage is only implied by the purpose statement; there is no explicit statement of when to prefer this over get_thread or list_replies, and no exclusions or prerequisites. The pagination sentence covers continuation, not tool selection.

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