مواقيت الصلاة

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

With no annotations, the description carries the full burden. It usefully discloses the default-date behavior and the important constraint that only a known set of city names is accepted, but says nothing about the effect of the calculation-method code, permissions, or failure behavior for unrecognized cities.

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, front-loaded with what the tool returns followed by how to invoke it. No filler, though it could be marginally tighter.

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 5-parameter, 0-required, no-output-schema tool, the description covers what is returned (the five prayer times) and both input paths. It does not describe return formatting or error responses, but nothing essential to correct invocation is missing.

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 60%; the description compensates by enumerating which city names are valid and clarifying that latitude/longitude are for any other location, which goes beyond the schema's single example. The method parameter's meaning is only in the schema, so it is not fully covered.

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+resource: returns the five daily prayer times for a city or coordinates on a given date (default today). This is clearly distinguishable from all siblings (Quran audio, hijri date, radio stations), so an agent can select it without opening the schema.

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?

Explains the two invocation modes clearly — pass a city from the known list (Makkah, Madinah, Cairo, Kuwait, UAE) or pass latitude/longitude for any other place — and notes the date defaults to today. It gives actionable context but no explicit when-not-to-use guidance or error/edge-case handling.

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