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

Annotations state readOnlyHint=true and destructiveHint=false; description adds that this tool presents an interactive player widget, has a default reciter ID behavior, and contains a caution about guessed reciter IDs pointing to the wrong reciter. Also discloses the 200-total-ayah limit. No contradiction.

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?

Description is front-loaded with purpose, then uses short labeled sections (RECITER HANDLING, Limits). Every sentence carries necessary operational information, no filler. Well-structured for an AI to parse.

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 tool with nested query objects, the description covers use case, reciter resolution, ayah key format, defaults, and limits. Output schema exists, so return values need not be described. The description is sufficient to invoke the tool correctly with no ambiguity.

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 already documents each parameter thoroughly (100% coverage). Description adds value by explaining the reciter lookup procedure, the default_reciter_id behavior, and the aggregate limit of 200 ayahs per request, which is not present in 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?

Clear verb+resource: 'Play Quranic ayah audio'. It specifies the interactive player widget and explicitly states when to use ('when the user asks to play/listen to ayahs'), distinguishing it from sibling search/translation tools.

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?

Explicitly states when to use, provides concrete conditional logic for reciter_id (always call lookup_reciters first, omit if not specified), and documents request limits. This goes beyond simple context to include a mandatory cross-tool prerequisite.

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