get_quran_verse

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

With no annotations, the description carries the full burden, and it does disclose meaningful traits: read-only retrieval, inclusion of a citation, and the strong constraint not to paraphrase or alter the text. It does not mention the locale fallback behavior for 'ur'/'id' (which lives only in the schema), so it stops short of fully covering behavioral edge cases.

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 tight sentences with the core purpose front-loaded and the quoting constraint as a supporting instruction. Nothing is redundant or padded.

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 simple two-parameter lookup with 100% schema coverage and no output schema, the description adequately conveys what is returned and the key citation/quoting behavior. Minor gaps remain around the locale fallback and audience teaching-mode behavior, but those are covered by the schema.

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%, so surah, ayah, locale, and audience are already documented with ranges, enums, and fallback notes in the schema. The description merely references surah and ayah and adds no syntax or format meaning beyond that, so the 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 and resource ('Returns one Quran verse by surah and ayah number') and names the exact returned artifacts (Tanzil Uthmani Arabic, Pickthall English, citation). This cleanly separates it from the plural sibling find_verses, which implies search rather than lookup by exact reference.

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 phrasing 'by surah and ayah number' implies the tool is for exact-reference lookup, and the instruction to quote rather than paraphrase is a usage directive. However, it never explicitly says when to use this versus find_verses, nor any exclusions, so guidance remains inferred rather than stated.

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