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

Annotations already declare readOnlyHint and destructiveHint, so the safety profile is covered. The description adds useful behavioral context by specifying what the result contains (series continuation, same-author works, similar reads) and that it matches the siftivo.com book page. It does not outline return structure, but for a simple read-only recommendation tool this is sufficient.

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 exactly two sentences, both earning their place: the first specifies input and output categories, and the second anchors the result to a known reference page. There is no repetition of schema or annotation data.

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?

With one parameter, no output schema, and read-only annotations, the description conveys the core behavior and a concrete reference point (siftivo.com book page). The reference is slightly opaque for an agent that does not know that page's structure, so a perfect score is not warranted.

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 fully documents the sole parameter: workId as a string from search_books, get_book, or a URL slug, with minLength 1. The tool description only paraphrases this with 'Given one book' and contributes no additional parameter semantics, aligning with the high-coverage baseline.

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 derives reading recommendations from a single book, enumerating the three output categories: next in series, more by the same author, and similar books. It also differentiates itself from related siblings by focusing on a single existing work as input, rather than titles or descriptions.

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?

Usage is implied through 'Given one book,' which suggests the tool applies when the caller already has a specific work ID. However, it does not explicitly name alternatives or exclusion criteria relative to recommend_from_titles, recommend_from_description, or get_series, leaving the selection to inference.

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