update_user_book_read

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

Without annotations, the description covers key behavior: it performs partial updates (preserves unspecified fields) and supports both page and audiobook progress. However, it does not disclose error handling or idempotency details.

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 two sentences with no redundant words. It front-loads the key action and then adds relevant detail.

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?

The description adequately covers the tool's purpose and key behaviors given the absence of an output schema. However, it could be more complete by mentioning any constraints (e.g., cannot update both progress types simultaneously) or return value expectations.

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?

All parameters are described in the schema (100% coverage). The description adds value by explaining the partial update behavior and clarifying that progress_pages and progress_seconds correspond to page and audiobook tracking, respectively.

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 action (Update) and the resource (reading date or progress entry). It mentions partial updates and support for both page and audiobook tracking, which distinguishes it from sibling tools like add_user_book_read (create) and delete_user_book_read (delete).

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 updating existing entries but does not explicitly state when to use this tool versus alternatives (e.g., add_user_book_read for new entries). It does not provide exclusions or context on prerequisites.

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