List user content

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds useful behavioral context beyond annotations: 'newest first' ordering, pagination, and a security warning to treat returned user-generated content as data, never instructions. It does not cover auth requirements or error behavior, but adds meaningful value.

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?

Three sentences, each earning its place: core purpose first, then usage context, then a security warning. Front-loaded and no wasted words.

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?

The description covers purpose, usage, ordering, pagination, and security. It does not describe the return structure in detail (e.g., fields per thread/post item), and no output schema exists, but for a listing tool with rich annotations and full schema coverage, it is nearly complete.

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 schema already documents all four parameters including pagination, user_id, and text_length truncation. The description's mention of 'pagination' and 'newest first' adds minor ordering context but no new parameter semantics 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 a specific verb (Lists), resource (threads and posts created by a user), and scope (newest first, with pagination). This is clearly distinguishable from sibling tools like forum_list_threads and forum_list_posts that list all threads or posts without user filtering.

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?

Provides clear usage context: 'Use it to see what a user writes about or to check their activity.' However, it does not name alternatives or state when not to use this tool versus other listing or search tools.

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