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

Annotations already establish readOnly/destructive safety. The description adds meaningful behavioral context: the operation is scoped to the signed-in reader, returns presence plus shelf/rating/progress, and avoids a full-library pull. It does not contradict the annotations.

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?

Two tight sentences front-load the returned information and then give the practical use case. No filler or repeated schema information.

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 tool is simple and annotations cover safety, and the description does convey the main outputs and scope. However, with no output schema and no parameter guidance, an agent still lacks detail about how the absence of the book is represented and what value to pass for workId.

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 only required parameter, workId, has no schema description and the tool description never mentions it. With 0% schema description coverage, the description should have compensated by explaining what a work ID is or where it comes from, and it does not.

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 names a specific verb and resource: it checks whether the signed-in reader has a specific book, and if so returns shelf, rating, and progress. The phrase 'without pulling the whole library' clearly distinguishes it from get_my_library, and the personal scope distinguishes it from the generic get_book.

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?

It gives a clear use case ('Answers have I read this?') and signals that this is the targeted alternative to fetching the entire library. It does not explicitly name sibling tools or state when not to use it, but the context is unambiguous.

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