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

With no annotations, the description carries the full burden. It does disclose that votes affect the evening review, but it omits critical behavioral traits: whether voting is idempotent, can be repeated, requires authentication, or has side effects on other data. The mutating nature is implied but not detailed.

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 extremely concise—one sentence that front-loads the action and a brief consequence. It earns its place by being efficient, though it sacrifices substance for brevity.

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 mutating action with no annotations, output schema, or parameter description, the definition is incomplete. An agent needs to know if this is safe to call, what the response is, and what 'id' refers to. The description only covers the core purpose and a hint of outcome, leaving significant gaps.

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?

The schema has one required integer parameter 'id', and the description provides zero information about it. With 0% schema description coverage, the description must compensate but doesn't. The agent is left to guess that 'id' refers to the idea's ID, which is not explicitly stated.

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 clearly states the action ('Back an idea with a vote') and the resource (idea), and it distinguishes itself from siblings like comment_idea and submit_idea by specifying the voting action. However, it could be more explicit about the exact scope (e.g., only for ideas) but it's unambiguous.

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?

No guidance is given on when to use this tool versus alternatives. It doesn't mention that voting is separate from commenting or submitting, nor does it state any prerequisites (e.g., must be logged in, voting limits). The agent has to infer usage from the name and sibling context.

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