reddit_get_replies_to_me

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

The description goes well beyond the annotations by explaining the diffing implementation, the deliberate avoidance of the privatemessages OAuth scope, the extra request cost, and the absolute read-only nature of the server with a specific list of impossible actions. This gives the agent strong behavioral context and matches the readOnlyHint annotation.

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 first sentence front-loads the core purpose, and the key behavioral notes are concise. The final paragraph about helpful participation and subreddit rules adds behavioral guidance but is somewhat tangential to tool invocation, keeping this from a perfect score.

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?

Annotations, output schema, and the detailed behavioral description cover much of the context. However, the lack of parameter semantics for 'since' is a real gap that affects correct invocation, and there is no explicit routing guidance among sibling tools.

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%, and the description does not explain either parameter. 'limit' and 'since' are somewhat self-explanatory names, but 'since' especially lacks any format, timezone, or semantic details, leaving the agent to guess what value it expects.

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 opens with a specific verb and resource: 'Find new replies to the user's own posts and comments.' This uniquely distinguishes the tool from siblings like reddit_get_my_activity, reddit_get_thread, and reddit_search_posts by scoping it to replies on the user's own content.

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 intended use is implied clearly by the first sentence, but the description does not explicitly state when to prefer this tool over alternatives, nor does it mention exclusions. It explains implementation trade-offs but not usage selection criteria relative to sibling tools.

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