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

The annotations already declare readOnlyHint=true and openWorldHint=false, so safety behavior is covered. The description adds useful context about the returned content (Bayan link, jarh wa ta'dil grade, related articles), but it does not mention behavior for unknown names, ambiguity/multiple matches, or response format beyond the general content.

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?

It is a single compact sentence that front-loads the resource and lists the useful return elements. There is no wasted text, though the phrasing 'A hadith narrator by name' reads more like an entity label than an action.

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 one fully documented parameter and annotations covering safety, the remaining burden is mainly explaining output and usage. The description explains the output content, which is important because there is no output schema, but it omits usage guidance and edge-case behavior.

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%: the sole 'name' parameter is documented with an Arabic example. The description only says 'by name' and adds no formatting, transliteration, or disambiguation guidance beyond what the schema already provides.

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 identifies a specific resource (a hadith narrator) and what the call returns: a link to his Bayan page, his grade in jarh wa ta'dil books, and related articles. It is distinguishable from siblings like get_hadith and get_article, though the retrieval verb is only implied rather than stated directly.

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?

There is no explicit guidance on when to use this tool versus get_hadith, get_article, or search. The word 'by name' hints at the input, but no alternatives, exclusions, or preconditions are stated.

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