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

The description asserts "Nothing is read or changed," while annotations declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true — a direct behavioral conflict about whether the call mutates state. Because the two structured and unstructured sources disagree, an agent cannot determine the actual safety profile; this is precisely the kind of contradiction that warrants a 1.

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?

It is short, but three of the four sentences restate the same point (the check isn't wired, the tool isn't supported, nothing changes). The non-functionality notice could be a single front-loaded sentence; the repetition adds length without adding information.

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 seven-parameter mutation-flagged tool with no annotations alignment and no output schema, the description should at minimum resolve the destructive-vs-noop conflict and name where rating actually happens. It leaves both open, so an agent cannot act correctly on it with confidence.

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?

Seven parameters (orgId, stars, callId, review, confirm, idempotencyKey, acknowledgedAmountUsd) have 0% schema description coverage and the description adds no parameter semantics whatsoever. Notably, acknowledgedAmountUsd and confirm hint at a monetary confirmation flow that is entirely unexplained, so the description fully fails its compensation duty.

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 communicates that this tool is meant to submit a post-call review but is currently a non-functional stub, which is the most decision-relevant fact for an agent. However, it never states the operation directly ("rate a call" only appears in the title), and it frames the action as belonging to a separate "post-call review API" rather than describing this tool's own purpose.

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?

"This tool is not yet supported" is a strong implicit signal not to call it, which is useful routing guidance. But no alternative is named — the description references an unnamed "post-call review API" rather than any sibling tool such as get_reviews, so an agent that wants to see or submit ratings is left without a destination.

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