get_iqama_time

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

No annotations are provided, so the description must fully disclose behavior. It mentions that the time includes a configured offset, which is useful. However, it does not state whether the tool is read-only, or describe any error or caching behavior.

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?

The description is extremely concise: two sentences. The first states the core purpose, and the second lists the valid input values. No unnecessary words.

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?

Given the tool's simplicity and lack of output schema, the description covers the basics. However, it does not indicate the format of the returned time, error handling for invalid inputs, or how the configured offset is set (via sibling tool).

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 description explains the 'prayer' parameter by listing valid values (fajr, dhuhr, asr, maghrib, isha). The 'date' parameter is not explained beyond its optionality and default in the schema. This provides good clarity for the required parameter.

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 tool returns the Iqama time for a given prayer, including the configured offset. However, it does not explicitly distinguish itself from related sibling tools like get_prayer_times or get_azan_text, which could cause confusion.

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 implies use when you need the Iqama time for a specific prayer, but it provides no guidance on when to avoid this tool, prerequisites, or alternatives. It is adequate but lacks comparative context.

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