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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, yet the description still adds real context: the size-budget truncation rule, the next_start_page_id and `_display` continuation hint, and the has_more flag. It also enumerates the returned page fields, which no structured field supplies.

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?

Front-loaded with the core action and bounded by an example, with each sentence carrying distinct information (defaults, truncation, alternative). Minor waste in the Arabic opener that restates the title rather than adding meaning.

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 return-shape burden and discharges it by naming the per-page fields, the has_more flag, and the truncation continuation keys. A caller has everything needed to invoke it and to resume a cut-short range.

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 value the schema does not: it restates the 1–20/default-5 constraint in context and points to shamela_list_downloaded_books for obtaining book_id. count and start_page_id semantics are otherwise fully owned by the schema.

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?

States a specific verb and resource: fetch N consecutive pages from a downloaded book starting at start_page_id. It explicitly names two siblings it is not — shamela_get_page (loop) and shamela_get_book_section (full chapters) — so an agent can disambiguate without opening any schema.

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?

Gives explicit when-to-use ('Faster than calling shamela_get_page in a loop'), a when-not with the alternative named ('For full chapters use shamela_get_book_section instead'), and the prerequisite discovery path via shamela_list_downloaded_books. Nothing about selection is left to inference.

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