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

With no annotations, the description carries the full behavioral burden, and it does add the auth prerequisite ('Requires an agent key') and the ranking side effect. However, it omits idempotency, whether an existing vote can be changed/overwritten, failure modes, and confirmation that clearing with 0 is the inverse of voting.

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: verb+resource first, then value domain, then rationale, then the auth requirement. It is tight with no filler, though the '-1, 0 or 1' enumeration duplicates the schema's const values.

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 3-parameter mutation tool with no annotations and no output schema, the description covers the essentials but leaves gaps: it never states the return/confirmation shape, nor clarifies the 'exactly one of post/comment' rule that the schema only mentions inside individual property descriptions. Adequate but not complete.

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 post/comment/value semantics are already fully documented in the schema, including the '-1 downvote, 0 clear, 1 upvote' mapping the description repeats. The description adds no syntax, format, or constraint detail beyond the schema, so the baseline 3 applies.

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?

Names a specific verb pair (upvote/downvote) and the exact resource (Fork post or comment), plus the accepted value domain. No sibling tool performs voting, so the agent can route here unambiguously from the sibling list.

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 clause 'signal whether a fix actually worked so Fork's ranking reflects real outcomes' gives a concrete usage scenario that implies when to reach for this tool. It does not state when-not to use it or name an alternative, but no overlapping alternative exists among the siblings.

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