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

Annotations already declare this as a destructive, idempotent, non-read-only mutation, so the safety profile is largely covered. The phrase 'Set or update' hints that an existing rating is overwritten, but the description never explicitly says the prior rating is replaced or clarifies what 'destructive' means in this context. The half-star example duplicates schema constraints rather than adding behavioral context.

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 the core action and the rating constraint front-loaded; every clause is purposeful and there is no boilerplate.

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 simple six-parameter mutation with full schema coverage and annotations supplying the safety profile, the description is minimally sufficient. However, it omits practical context an agent needs, such as whether a prior rating is replaced and how this relates to clear_rating, leaving the description thinner than it should be for a destructive tool.

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 the schema already explains title matching, item_id precedence, rating range, and season/episode conventions. The description only restates the half-star constraint that is already encoded in the schema, adding almost no parameter meaning beyond structured fields.

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 states a clear verb and resource ('Set or update user rating'), so an agent immediately knows the tool's job. It does not differentiate from siblings such as clear_rating or set_review, keeping it at a 4 rather than 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?

There is no guidance on when to use this versus clear_rating (to remove a rating), set_review (for review text), or update_status. The agent is left to infer usage from the name and schema alone.

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