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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial context beyond them: truncation via max_pages, early stop on a character budget, the truncated flag, and continuation via next_start_page_id plus a _display hint. This more than meets the reduced bar annotations impose.

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 definition is front-loaded with a short purpose statement followed by mechanism, limits, and workflow, and every sentence carries information. The bilingual opening is slightly redundant but not wasteful.

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 burden of describing returns and does so: it explains the truncated flag, next_start_page_id continuation, the _display hint, and how structuredContent/response_format interact. An agent has everything needed to call it correctly and to paginate through long sections.

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 behavioral meaning to max_pages by tying it to the truncation flag and to continuation semantics. It does not go deeper on response_format, which the schema already documents thoroughly.

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 opens with a specific verb+resource ('Fetch every page under a chapter title') and immediately clarifies the resolution mechanism (next-sibling-title boundary in per-book SQLite). This is clearly distinguishable from sibling tools like shamela_get_page (single page) and shamela_get_pages_range (arbitrary range) because it is keyed on a chapter title_id.

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 states the workflow explicitly ('Use shamela_get_toc to find title_ids, then this tool to read the matching section') and supplies a concrete invocation example. It does not, however, name when a caller should prefer a sibling (e.g. get_page or get_pages_range) instead, so it lacks exclusions.

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