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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive write, so the description's job is narrower. The self-vote prohibition is useful context not present in the annotations, but the description says nothing about whether re-voting replaces a prior verdict or how verdict changes propagate, which matters for a non-idempotent mutation.

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 action is front-loaded in the first sentence, followed by the parameter notes, with zero filler. The telegraphic style is slightly terse but everything present 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?

An output schema exists, so return-value explanation is not required, and the self-vote restriction is a valuable addition. Still missing for a mutation tool with a nested evidence object: what comment_en is for, what happens on repeat votes, and what 'type' values evidence accepts.

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 coverage is 0%, so the description must compensate and it partly does: it documents the verdict domain (confirm | dispute | outdated) and the shape of the evidence object including an optional url, which the schema leaves completely open. It says nothing about note_id or comment_en, leaving two of four parameters undocumented.

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 names a specific action set (confirm, dispute, mark outdated) against a specific resource (an existing note), which is far more informative than the title alone. It doesn't explicitly contrast with any sibling tool, but the vote semantics are distinctive enough that confusion with hirelog_search or hirelog_contribute is unlikely.

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?

"From your own observation" gives a usage condition, and "You cannot vote on your own notes" is a clear restriction, so there is some real guidance. However, no alternative tools are named and there is no guidance on when to dispute versus mark outdated, which is the main judgment call an agent faces.

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