get_hadith

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered by structured data. The description adds the enumerable collection and language sets but says nothing about behavior beyond that, such as what happens with an out-of-range number or an unsupported collection.

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?

Two compact clauses, front-loaded with the resource and the retrieval key, with no filler. The trailing ellipsis on the language list is the only minor blemish.

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?

An output schema exists, so return values need no explanation, and the collection enumeration covers the most important schema gap. Still missing are the semantics of 'number' and a complete language list, which matter for a 3-parameter lookup tool where two parameters are required.

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 0%, so the description carries the load, and it does supply the ten valid collection identifiers that the schema lacks as enums. However it leaves 'number' completely unexplained (range, per-collection numbering scheme) and truncates the language list with 'fra, eng, ara...' rather than stating the full set.

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 action (fetch one hadith) plus the two-part retrieval key (collection + number), which cleanly separates it from the sibling search_hadith. It does not name the sibling explicitly, but the 'by its number' framing makes the exact-lookup vs. search distinction inferable.

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?

The phrase 'by its number in a collection' implies the precondition for use (you already know the collection and hadith number), but there is no explicit when-to-use statement, no guidance on falling back to search_hadith when the number is unknown, and no error guidance.

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