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

The parenthetical '(toggles)' discloses that rating is a flip rather than a set — meaningful context that explains the non-idempotent annotation and warns agents against accidental double-toggling. The self-rating restriction is a business rule absent from the annotations and schema. It stops short of describing the write's effect on scores or its return shape.

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?

Two short sentences with zero filler; the core action and the restriction are both front-loaded and immediately actionable.

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 3-parameter mutation with annotations covering the safety profile and no output schema, the description supplies the two facts an agent most needs: the toggle behavior and the self-rating block. It leaves character_id semantics and the effect of a rating on standings unstated, a minor gap.

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 33% and character_id is undocumented in both schema and description. The description echoes the category enum values but adds no meaning beyond the schema, and 'a contestant' only loosely identifies character_id. Baseline 3 for a low-coverage schema where the description fails to compensate.

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 (rate) and resource (contestant), and names the two permitted categories ('likable' or 'surprising'). No sibling tool performs ratings, so differentiation is implicit rather than stated, which keeps it just below a 5.

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?

Provides a precondition ('You can't rate your own') which is a useful constraint, but gives no guidance on when to use this versus other engagement tools like predict or reflect_on_date. Usage context is only implied.

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