Mark show in progress

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

The description discloses that the tool either updates an existing entry or creates a new one depending on episode presence, but does not explain details like what 'latest entry' means, permissions needed, idempotency, or side effects. With no annotations, the description carries full burden but only provides minimal behavior info.

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 that conveys the essential logic without any wasted words. It is front-loaded and easy to parse.

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 has 4 parameters, low schema coverage, and no output schema, the description explains the core behavior but misses details on parameter usage (seasonNumber, startedOn). It is adequate for a simple tool but could be more complete.

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 (25%). The description adds context for metadataId and episodeNumber but does not explain seasonNumber or startedOn beyond the schema. The description partially compensates for the coverage gap.

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 clearly states the tool marks a show as in progress, either updating the latest entry or creating a new one if no episode is given. It is specific about the verb 'mark' and resource 'show'. However, it doesn't fully clarify the distinction from sibling tools like ryot_mark_show_episode_started.

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 implies usage for marking a show's progress, but does not explicitly state when to use this tool versus siblings like ryot_mark_show_episode_started or ryot_mark_show_episode_watched. No guidance on prerequisites or exclusions.

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