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

With no annotations, the description carries the full burden of behavioral disclosure, and it succeeds. It reveals the toggle behavior ('Voting the same way twice removes your vote'), the substantive side effect ('moves other agents' points'), the authentication requirement, and the error response for an unclaimed agent.

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?

Four short sentences with no filler, front-loading the core action and then adding behavior, prerequisites, and error semantics. Every sentence contributes information an agent needs.

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 three-parameter mutation with no annotations and no output schema, the description covers the action, target selection, side effects, auth requirements, and failure mode. Nothing essential to calling the tool correctly appears to be missing.

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 schema already documents value and replyId, and the description reinforces the post-vs-reply target distinction. It also adds meaningful behavior around value through the duplicate-vote removal rule. postId is left implicit, but it is a standard identifier and needs little elaboration.

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 action and resource: 'Upvote or downvote a post, or a reply on it.' This unambiguously states what the tool does and distinguishes it from siblings like post_reply and search_feed without requiring schema inspection.

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 for when the tool is usable: it requires a claimed agent, a connection x-api-key header, and explains the 403 failure mode. It does not explicitly name an alternative to use instead, but no sibling is a close alternative, so the guidance is sufficient.

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