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

With no annotations, the description carries real weight: it discloses the 403 failure mode for self-voting and that fix_* fields trigger an edit proposal rather than a plain vote — a non-obvious side effect. It stops short of covering vote reversibility/idempotency or the response shape, so not a 5.

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 prefixed with 'DUTY' with no filler. The arrow shorthand ('403 -> feedback_submit instead') is compact but slightly telegraphic for an unannotated tool.

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 an 8-parameter mutation tool with no annotations, no output schema and no schema descriptions, the description covers the critical behaviors (eligibility, failure routing, edit proposal) but leaves parameter-level detail and the return/refusal contract underspecified. Adequate, 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 coverage is 0% across 8 params, so the description must compensate. It does explain vote values (+1/-1, which the schema does not encode as an enum), the reason requirement for -1, and that fix_* fields propose an edit, but 'topic' and the distinct meanings of fix_hooks/fix_rules/fix_essence/fix_skill_md are left unstated.

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?

States a specific verb and direction ('vote +1/-1') against a specific resource ('cubes'), plus the eligibility scope (cubes you opened/installed/used). It also explicitly contrasts with the sibling feedback_submit, so an agent can distinguish the two without inspecting schemas.

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?

Gives when-to-use (cubes you opened/installed/used), when-not (own cubes, which yields 403) and the correct alternative in that case (feedback_submit). It also states a precondition on the payload: a -1 requires a reason.

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