reddit_vote

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly indicates the mutation (cast/clear vote) and the direction values, including the ability to clear a vote with 0. However, it omits details like authentication requirements, idempotency, rate limits, or what happens if the target is invalid, which would be useful but are not critical for a simple voting action.

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?

A single, front-loaded sentence with no filler. It conveys the action, the possible directions, and the target type efficiently. 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?

For a simple two-parameter tool with full schema coverage and no output schema, the description is mostly complete: it specifies what the tool does, what the target is, and what the direction values mean. It lacks explicit auth or error-behavior context, but the simplicity of the operation makes this a minor gap rather than a critical omission.

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 fully documents both parameters. The description adds only a slight contextual reinforcement ('post or comment') but no additional syntax, format, or edge-case guidance beyond what the schema provides. 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 states a specific verb ('Cast or clear') and resource ('upvote/downvote on a post or comment'), making the tool's function immediately clear. It also naturally distinguishes this from siblings like reddit_submit_post, reddit_save_post, or reddit_read_thread, since voting is a unique action in the sibling set.

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 gives clear context: use this tool when you want to set or remove a vote on a Reddit post or comment. It does not explicitly name alternatives or exclusions, but the purpose is specific enough that an agent can infer when to select it over the other reddit tools.

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