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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, idempotentHint=true), yet the description adds substantial behavior beyond them: the Arabic-folding rules that make «شعبه» find «شعبة», AND-token matching across name/lineage/nisba fields, the ranking rule (dossier size, death-year tiebreak), and an explicit warning that common names must be disambiguated by death year and grade.

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 Arabic title and the core purpose before diving into folding, ranking, and examples. It is dense but nearly every sentence carries distinct information; it runs slightly long, which keeps it off a 5.

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?

For a search tool whose annotations already declare it a safe read, the description covers everything an agent needs: the resource, normalization behavior, result ranking, disambiguation pitfalls, and example invocations. No output schema exists, but the caller consumes narrator_ids, which the description explains, so nothing material 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 description coverage is 100% and each parameter is already documented in the schema, so the baseline is 3. The description mostly restates the schema's own folding/AND/ordering text rather than adding new parameter-level meaning, though it does add the paging motivation with a concrete figure («محمد بن» matches 3,620).

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 — find a ḥadīth narrator by name in Shamela's rijāl register — and pins down the scope (18,989 narrators, death years 2-774 AH). It also distinguishes itself from siblings by declaring itself 'the entry point for ʿilm al-rijāl: every other narrator/isnād tool takes the narrator_id this returns.'

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?

Clearly frames when to reach for it (searching for a narrator by name, before calling any narrator/isnād tool that needs a narrator_id) and supplies two concrete call examples. It stops short of explicit when-not guidance, so it falls just under a 5.

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