rate

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

With no annotations, the description carries the burden of disclosing side effects. It explicitly states that rating an item not on a list auto-files it, and details the mapping for different content types. The warning to trust the response rather than predict the delta adds useful transparency. However, it does not cover behaviors for already-rated items, permissions, or reversibility.

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?

The description is concise, with the primary purpose front-loaded in the first sentence. The subsequent sentences add necessary behavioral context without excessive verbosity. It could be slightly more structured, but it is efficient and readable.

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?

Given the tool's complexity (mutation with side effects), the lack of annotations, and zero schema coverage, the description is incomplete. It does not explain parameter semantics, what the output schema will contain, error conditions, or prerequisites like authentication. The warning about the delta hints at a response but does not describe it.

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 explain the parameters, but it does not. It only hints at the rating range ('1-10') and says nothing about the structure of 'items' or the meaning of 'type'. The agent is left without essential information to construct valid arguments.

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 opens with a specific verb and resource: 'Rate titles 1-10.' It also discloses a key side effect (auto-filing) that distinguishes this from sibling tools like get_ratings (read-only) or set_status (explicit status change). The purpose is unambiguous and differentiated.

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 explains a behavioral consequence (auto-filing) but provides no explicit guidance on when to use this tool versus alternatives. It does not mention set_status or mark_watched, nor does it state conditions for choosing this tool over them. The context is implied rather than stated.

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