delete_my_rating

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

Annotations already declare destructiveHint=true and idempotentHint=true, and the description's 'Delete' is consistent with those. The word 'authenticated user's' adds the ownership/scoping context, but the description stops short of explaining response behavior or the no-op case.

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, front-loaded sentence with no filler. Every word contributes to identifying the action and target.

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 one-parameter mutation with strong annotations covering destructiveness and idempotence, the description plus schema is sufficient to invoke the tool. The main missing piece is return/response behavior, which is partly covered by the absence of an output schema and the idempotence hint.

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?

With schema description coverage at 0%, the description carries the full burden for explaining title_id, but it only indirectly implies that the parameter identifies the title whose rating is deleted. It does not describe the required format or how to obtain a valid title_id.

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 phrase 'Delete the authenticated user's IMDb rating' uses a specific action verb and names the exact resource, making the tool's purpose unmistakable. It also differentiates itself from sibling tools such as set_my_rating, get_my_rating, and list_my_ratings.

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?

The description makes clear the target is restricted to the authenticated user's own rating, which implies the tool is for removing one of the current user's ratings. It does not explicitly state when to prefer this over set_my_rating or provide alternatives/exclusions.

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