reddit_save_post

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It does disclose the dual save/unsave behavior and that comments as well as posts are supported, which goes beyond the tool name. However, it does not mention whether authentication is needed, how repeated saves are handled, or what happens on failure.

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 a single concise sentence with no filler. It front-loads the operation, then specifies the resource and target. Every word earns its place.

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 tool is simple with only two parameters and no output schema, and the description adequately states what is acted on and the two possible operations. Still, the lack of any annotation means an agent has no explicit guidance about authentication prerequisites or result handling, leaving a modest but real gap.

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?

The input schema covers both parameters with clear descriptions, and the description's 'save or unsave' and 'post or comment' wording aligns with those parameters. It adds no extra format, constraint, or nuance beyond the schema, so baseline 3 is appropriate.

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 uses specific verbs ('save or unsave') and names the resource ('post or comment') and destination ('account bookmarks'). This clearly distinguishes the tool from sibling submission, voting, messaging, and browsing tools even without naming alternatives.

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: an agent should call this when the user wants to bookmark or unbookmark a Reddit post or comment. However, it does not explicitly state when to prefer this tool over alternatives, mention authentication requirements, or specify any exclusions.

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