نص آية محددة

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

With no annotations, the description carries the full behavioral burden. It implies a read-only retrieval and states that the return is the verse text, but it omits error behavior for out-of-range numbers, response format, and any auth or rate-limit context.

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?

One front-loaded sentence states the operation and its two inputs with no filler or repetition. It is appropriately sized for a simple lookup tool.

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?

The tool is simple and the schema fully documents both numeric parameters; the description states what is returned (verse text), so an agent can call it confidently. Minor gaps remain around invalid-range behavior and response format, but for this complexity level the description is adequate.

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% and both parameters carry their own Arabic descriptions with numeric ranges. The description repeats the surah/ayah inputs without adding format, counting, or edge-case semantics beyond the schema, so the baseline of 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 precise verb+resource: returns the text of one specific Quranic verse identified by surah and ayah numbers. The scoping phrase 'آية واحدة بعينها' implicitly differentiates it from search_quran and the audio/list siblings, though no sibling is named explicitly.

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?

Usage is only implied by the required surah/ayah inputs; there is no explicit when-to-use, when-not, prerequisite, or routing guidance. It never tells the agent to prefer search_quran for discovery or what to do if the verse does not exist.

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