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

Annotations already declare readOnlyHint=false and idempotentHint=true, so the mutation/idempotency profile is partly structured. The description still adds real operational context beyond them: re-voting replaces the prior vote, vote and report must agree, and `report` does not affect the rating. No contradictions with annotations.

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?

Front-loaded with the core action and scoping before the exceptions, and each clause does work. It is longer than strictly necessary, with some redundancy between the vote definition in the description and the schema's `vote` description.

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 four-parameter mutation tool with no output schema, the description covers the full decision surface: rating criteria, anti-patterns to avoid, report semantics, re-vote behavior, and the correct sibling for off-topic issues. Nothing an agent needs to call it correctly 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 all four parameters are already documented, making 3 the baseline. The description reinforces that `method`/`url` must match `discover` output exactly and explains the intent of `report`, but adds little syntactic detail the schema does not already carry.

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 resource ('rate a documented endpoint you called') and immediately anchors the identifiers to how `discover` returns them. It is clearly distinguishable from siblings like `feedback`, which it names as the tool for taskfuel-level problems.

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?

Explicit when-to-use both directions (up for expected/useful, down for broken or not worth the price), plus a negative list of things that must NOT be down-voted (missing catalog entry, own bad arguments, worked-but-wrong-fit) and an explicit routing rule to `feedback` for platform issues. One-vote-per-endpoint and changeability are also stated.

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