rate_collection_item

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is partly covered. The description adds genuinely useful context beyond them: the 0–5 scale, that 0 clears the rating, and critically that the call dry-runs by default before committing.

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?

A single tight sentence that front-loads the core action, then adds the two most decision-relevant facts (reset semantics, dry-run default). No wasted words.

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?

There is no output schema and 0% schema coverage across 4 params, so the description carries the burden. It covers the primary rating and dry-run semantics but omits what release_id/instance_id identify and what the dry-run response returns, leaving gaps for an agent.

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 0%, so the description must compensate; it defines rating (0–5, 0 clears) and implies dry_run's default behavior. However, release_id and instance_id remain completely undocumented, leaving half the parameters unexplained.

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 (Set a star rating) and resource (a collection instance), so the action is unambiguous. It doesn't differentiate itself from siblings like set_collection_field, but the verb+resource pairing is clear enough to identify the tool.

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?

Uses the quasi-guidance of '0 clears it' and 'Dry-run by default', which tells the agent how to reset a rating and that side effects are deferred. However, it names no alternative and gives no explicit when-to-use versus the many other collection-mutation siblings (add_to_collection, set_collection_field, move_collection_item).

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