Log Read Book

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

No annotations provided, so the description carries full disclosure burden. It implies a write operation but does not state side effects, whether duplicates are created, auth requirements, or what happens when book_id is omitted vs provided. The presence of book_id and multiple optional note fields (notes, review, private_notes) raises behavioral questions the description doesn't address.

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?

Single efficient sentence that front-loads the action and key fields. No waste, appropriately sized for a straightforward logging tool.

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?

Output schema exists so return values need not be described. However, with 8 parameters, no annotations, and an overlapping trio of text fields (notes/review/private_notes), the description is incomplete for an agent to call this correctly — it should clarify field intent and whether book_id resolution creates or links records.

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 100%, so all parameters are documented in the schema. The description adds meaning by clarifying rating scale (0-5 stars) and that review is optional, but doesn't explain the distinction between notes, review, and private_notes — a real ambiguity given three overlapping text fields.

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?

Clear verb (Log) and resource (completed book) with key fields named (rating, review, date). Distinguishes from read-oriented siblings like search_books and get_reading_list by being a write/log tool. Lacks explicit sibling differentiation but the verb itself separates it well.

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 when-to-use guidance, no mention of the sibling log_watched_media, log_restaurant, log_sensory_item which follow the same logging pattern. No exclusions or prerequisites stated. The agent must infer this is for finished books only.

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