mark_series_unread

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

With no annotations, the description bears full responsibility for behavioral disclosure. It states the bulk action ('every book') but does not explain potential side effects, reversibility, or whether reading progress is reset. This is a significant gap for a mutation tool.

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 concise sentence that efficiently conveys the core action. Every word contributes value, with no redundancy or filler.

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?

While the tool is simple with one parameter and an output schema exists, the description lacks details about the effect on reading progress and any prerequisites or consequences. It is minimally viable but leaves clear gaps given the mutation's broad scope.

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?

The schema provides no description for 'series_id', and the schema coverage is 0%. The description does not mention the parameter or its semantics, forcing the agent to guess that 'series_id' identifies the series. This fails to compensate for the lack of schema info.

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 'Mark every book in a series as unread' uses a specific verb and resource, clearly stating the action and scope. It distinguishes itself from siblings like 'mark_series_read' and 'mark_book_unread' by specifying the bulk series-level unmarking.

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 provides no guidance on when to use this tool relative to alternatives like 'mark_series_read' or 'mark_book_unread'. No context or exclusions are given, leaving the agent to infer the appropriate usage.

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