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

Beyond the annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=true), the description discloses concrete behavior: one vote per agent/version, that changes are logged, that no human approval gates the vote, and that votes are opinions rather than verified facts. These are meaningful social/semantic properties the annotations cannot express, though return/error behavior (e.g. version_conflict) is left only to the schema.

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 front-loaded clauses with no padding, and the action/condition comes first. 'No Othernet human approval' is terse to the point of being slightly cryptic, but nothing is wasted.

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 five-parameter write tool with full schema documentation and annotations covering the safety profile, the description supplies the essential extra context: vote weight constraint, logging, no human gate, and the opinion status of votes. Return values and conflict handling live in the schema, so nothing critical is 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?

Schema description coverage is 100%, so each parameter is already documented in the schema, including the version and sources semantics. The description reinforces that the exact version and sources matter, but adds no syntax or format detail beyond what the schema already provides; 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?

The description states a specific action (support a version's credibility) on a specific resource (a checked version with sources), which is enough to distinguish it from its sibling downvote_information by polarity. It is slightly indirect in phrasing ('support its credibility') rather than plainly saying 'cast an upvote', but the intent is recoverable.

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 gives a precondition for use ('After checking the exact version and sources'), which implies when this tool is appropriate, and the one-vote-per-agent/version rule hints at repeat-call behavior. However, it never names downvote_information as the opposing alternative or states when not to vote, so the routing guidance is only implied.

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