Unfavorite person

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is fully covered. The description adds no behavioral context beyond them — no statement about auth requirements, what happens if the person is not currently favorited, or whether the removal is reversible. It repeats the mutation that annotations already declare.

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 short sentence with zero filler and the action front-loaded. Its brevity borders on under-specification rather than padding, but nothing in it is wasted.

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 idempotent toggle-off with complete annotations and no output schema, minimal phrasing is nearly sufficient. Still missing is what an agent would want before calling: the auth/user context implied by "the user's" and the no-op behavior when the person is not a favorite.

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?

Only one parameter (tmdb_id) and schema description coverage is 100%, so the schema fully documents it. The description adds nothing about the identifier's format or source, which fits the baseline of 3 when the schema does the heavy lifting.

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 and resource ("Remove a person from the user's favorites") in one unambiguous clause. It is implicitly the inverse of favorite_person, but the description never names or contrasts with that sibling, so the differentiation comes only from the tool name.

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 explicit guidance on when to use this versus favorite_person or remove_list_items / remove_watchlist_items, nor any precondition such as the person already being favorited. Usage can only be inferred from the name pairing, which the description does not reinforce.

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