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

Annotations already declare read-only/idempotent/no-destruction, and the description still adds substantial non-obvious behavior: book_date is usually the author's death year (not composition), downloaded is true only under a dual condition, cover absence does not imply no scan, and same_group entries must not be double-counted as sources. This is exactly the kind of field-level semantics annotations cannot carry.

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 core purpose is front-loaded in the first sentence, and most of the parenthetical caveats (book_date, downloaded, same_group, notes) earn their place given there is no output schema. It is dense and slightly redundant with the schema on cover-token cost, but not padded.

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 no output schema, the description carries the full burden of return-value documentation, and it delivers: it names the returned fields and their pitfalls, explains the notes array as non-fabricable citation fields, and gives id-resolution guidance. Nothing an agent needs to interpret the response is missing.

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 coverage is 100%, so the baseline is 3, but the description adds genuine decision context for include_cover (why to suppress it, that absence is not meaningful, that ~1,368 of 8,594 books have one) and reinforces the cover/scan distinction. It does not, however, add anything about response_format beyond what the schema states.

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?

Opens with a specific verb+resource ('Fetch full metadata for a book by book_id') and immediately enumerates the fields returned, so an agent knows exactly what this provides versus shamela_get_book_parts, shamela_get_toc, or shamela_get_page. It also disambiguates scope from shamela_list_downloaded_books by stating it 'works on any catalog book whether downloaded or not.'

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?

Explicitly routes id discovery to shamela_resolve('book name') or shamela_list_downloaded_books, and clarifies the downloaded-vs-catalog scope. It stops short of stating when to prefer a sibling like shamela_brief or shamela_get_book_parts, but the context for use is clear.

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