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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's added value is the edge-case behavior: single-volume books return is_multi_volume:false and an empty parts array, except one retained part label because get_citation prints it. That is meaningful behavioral disclosure beyond 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?

Front-loads the purpose, then the return shape, then the edge case, then the example and the id-lookup pointer. Most sentences earn their place, though the leading Arabic restatement of the title adds no information and the return-field enumeration is dense.

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?

There is no output schema and no rich annotation surface for return values, so the description carries the full burden — and it does, spelling out every returned field plus the single-volume special case. An agent has everything needed to call and interpret this tool.

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 description coverage is 100% and the enum on response_format is fully documented in the schema itself, so the description adds little parameter meaning. It provides an example call, which is mildly reinforcing but not new semantics — baseline 3 applies.

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+resource: list the volumes/parts of a multi-volume book, then enumerates the exact returned fields (is_multi_volume, total_pages, parts with part name/page_count/first_page_id/last_page_id). This lets an agent distinguish it from siblings like shamela_get_toc and shamela_get_book 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 a clear motivating context ('Useful to know whether a citation needs a part designator') and routes the agent to shamela_list_downloaded_books for obtaining book ids. It does not, however, state when to prefer this over shamela_get_toc or shamela_get_book, so no explicit exclusions are offered.

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