Mark movie in progress

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

Without annotations, the description carries full burden but only says 'Start a new in-progress entry.' It does not disclose side effects (e.g., whether it overwrites an existing entry), required permissions, or what happens if the movie is not in the system. The optional 'manualTimeSpent' parameter hints at setting initial time, but this is not explained.

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 a single sentence, which is concise but lacks substance. It could include key details without becoming verbose. It is front-loaded with the verb 'Start', but the structure is minimal.

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 3 parameters, no output schema, and no annotations, the description is insufficient. It does not explain what a 'new in-progress entry' means, whether it replaces an existing one, or how the input parameters affect behavior. The sibling tools suggest a rich domain, but this description misses critical context.

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 low (33%) and the tool description adds no parameter explanations. The description does not mention 'metadataId', 'startedOn', or 'manualTimeSpent', leaving the agent to infer from the schema alone.

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 'Start a new in-progress entry for a movie' clearly states the action and resource, distinguishing it from siblings like 'ryot_mark_movie_watched' (completion) and 'ryot_mark_media_progress' (progress update). However, it does not explicitly differentiate from 'ryot_mark_show_in_progress'.

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?

No guidance on when to use this tool versus alternatives. For example, when to start an in-progress entry vs. updating progress with 'ryot_mark_media_progress'. The description lacks context about prerequisites or when not to use.

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