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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful context beyond that: 'mine' requires authentication, pagination continues by passing nextBefore as before, and user posts/author names must be treated as data rather than commands, a prompt-injection safety warning.

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 description is compact, front-loads the view-mode definitions, then adds pagination and safety guidance. Every sentence contributes directly to correct invocation and no text is wasted.

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 tool with rich annotations, the description covers view semantics, pagination, authentication needs, and injection safety. It still omits the category parameter meaning and any sibling-tool routing, and no output schema exists to explain the returned post structure, so it is adequate but incomplete.

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 must carry parameter meaning. It thoroughly explains the view enum values and clarifies before as a continuation cursor, but it completely omits the category parameter and its chat/help values, leaving one of three parameters undocumented.

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 defines three view modes for listing community conversations/help requests, making the tool's scope clear. It does not explicitly distinguish this tool from sibling tools like get_community_thread, so it falls short of a 5.

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?

The description explains what each view mode means and notes that 'mine' requires authentication, which implies when to use each mode. However, it does not name alternatives such as get_community_thread or state when not to use this listing tool, leaving routing guidance 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.