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

With no annotations, the description carries the full behavioral burden. It usefully discloses the return contents (reference, Tanzil Arabic, Pickthall English) and provides a concrete instruction: 'Quote the Arabic exactly.' This is meaningful behavioral context beyond the schema, though it does not cover rate limits, errors, or ordering.

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 sentences with no filler. The core search behavior is front-loaded, the return format is stated, and the exact-quoting instruction is a valuable addition that earns its place.

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 description covers the key operational facts: what it searches, what it returns, and the exact-quoting requirement. The schema fills in parameter details. It could be more complete with explicit guidance on choosing locale or distinguishing from get_quran_verse, but for a simple search tool it is largely 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?

The schema already describes all three parameters with 100% coverage, so the baseline is 3. The description adds little beyond confirming the query is a topic keyword, but it does not explain limit or locale semantics, leaving that to the schema.

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 clearly states a specific action ('Searches AskSakina's thematic index') and a specific resource ('Quran verses by topic keyword'). It does not explicitly name sibling tools or contrast itself with them, though the 'thematic index by topic keyword' phrasing implies a distinction from get_quran_verse.

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 topic keyword' gives some implied guidance about when to use this tool, but it does not explicitly state when to use it versus alternatives like get_quran_verse, nor does it provide exclusions or conditions. The guidance is 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.