List User Activity

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It does disclose the return format (JSON with items and meta) and pagination via next_cursor, which adds value. However, it does not mention authentication requirements, rate limits, or error behavior, which is a gap for a tool with no 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?

The description is exactly two sentences, front-loaded with the action ('List a user's recent posts and/or comments'), followed by the return format. No wasted words, and every sentence carries meaningful 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?

There is no output schema, but the description provides the return structure with items and meta, covering pagination and item types. It does not cover authentication or error scenarios, but for a simple list tool with clear schema docs for parameters, this is nearly complete. The main missing piece is explicit usage context relative to siblings, which is already addressed under usage guidelines.

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 detailed parameter descriptions, so the baseline is 3. The description adds extra semantics by explaining the response structure (items with kind, meta with next_cursor) and how it relates to pagination parameters, going beyond a simple restatement of 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?

The description clearly states 'List a user's recent posts and/or comments' with a specific verb and resource, and distinguishes it from sibling tools by focusing on user-specific activity rather than general feeds or profile lookups.

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 implies it is for retrieving a user's post/comment history, but it does not explicitly state when to use this tool instead of alternatives like reddit_get_user or reddit_list_posts. No exclusions or alternative guidance is provided.

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