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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds nothing beyond that — no note that removing a non-favorited handle is a no-op (which the idempotent hint implies), no auth requirements, no effect on the author's side.

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?

One front-loaded sentence with no filler; the operation is stated immediately. The trailing CLI snippet is compact but cryptic enough that it earns only partial credit.

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 single-parameter tool with annotations and no output schema, the minimum is covered. Still missing are confirmation of what the call returns (updated favorites list? ack?), whether the handle must omit or include the '@', and behavior when the author isn't favorited.

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 coverage is 0%, so the description must carry the parameter burden. It does clarify that handle refers to an author's handle and shows the "@handle" notation, which adds real meaning. However the example `unfav @handle a8r` introduces an unexplained second token not present in the schema, leaving format expectations ambiguous.

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 + resource: "Remove an author (@handle) from your favorites," which is distinct from siblings like favorite, list_favorites, and unfriend. The parenthetical CLI form reinforces what is being removed. It does not explicitly contrast with sibling tools, keeping it 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?

Usage is implied by the inverse of favorite and by list_favorites/unfriend existing as siblings, but the description never says when to call it versus those alternatives or what preconditions apply. No exclusions or routing guidance are given.

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