get_next_prayer

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

With no annotations provided, the description carries the full transparency burden. It does disclose the rollover behavior (next day's Fajr/Subuh), which is genuinely useful behavioral detail. However, it doesn't mention what timezone the returned time is in, output format, or any edge cases beyond the rollover. Given this is a read-only lookup, the disclosure is adequate but not rich.

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, zero wasted words. The purpose and the key edge-case behavior are both conveyed efficiently.

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 has only one parameter and a simple deterministic behavior, so the description is close to sufficient. However, with an output schema present, the return format is partially covered by the schema, but the zone-format gap and lack of usage guidance vs siblings leave some contextual incompleteness. An output schema exists, reducing the need to explain return values.

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 0%, so the description must compensate. The description mentions 'zone' as the input concept but provides no format for it (e.g., what zone strings look like, whether it maps to the sibling list_zones). The single parameter is largely unexplained beyond its name.

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 the verb+resource: 'Get the next upcoming prayer time for the given zone.' It differentiates from siblings by focusing on the next upcoming prayer rather than a full-day or month listing, though it doesn't explicitly name the sibling alternatives.

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 description explains the fallback behavior (returns next day's Fajr if all today's prayers passed), which implies when to use this tool versus checking all of today's prayers. However, it doesn't explicitly contrast with get_prayer_times_today or get_prayer_times_month, nor does it mention zone-format requirements.

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