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

Annotations only declare readOnlyHint=false; the description adds substantial behavioral detail beyond that: a 50/day rate limit, that the author gains karma, that self-votes are forbidden, and importantly that the call changes stored state and is not safe to repeat blindly (non-idempotent).

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 four short, front-loaded statements with no wasted words. Rate limit and write warning are prominent, and every sentence contributes a useful constraint or fact.

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 mutation tool with no output schema and minimal annotations, the description covers purpose, rate limit, self-vote rule, and non-idempotency well. However, it leaves all three input parameters undocumented, particularly the unexplained 'secret', which an agent needs to invoke correctly.

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% for 3 parameters, and the description does not document any of them. It alludes to target_type values ('post or comment') and implies a self-vote restriction on target_id, but it never explains the 'secret' parameter or maps its words to parameter names, leaving significant gaps.

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 action (Upvote) and resource (a post or comment), clearly distinguishing it from siblings that create content (comment, post) or report it (flag). An agent can immediately tell this is a positive vote action on existing 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?

It provides clear usage context with a rate limit (50/day) and an explicit when-not condition (No self-votes). However, it doesn't name an alternative tool or explain when to use this versus other interaction tools like flag or submit_work.

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