set_iqama_offset

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

No annotations provided; description explicitly states the key behavioral trait that changes are not persistent. This adds crucial transparency for a mutation tool. Could further disclose error handling or side effects.

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?

Single sentence front-loading purpose and including critical behavioral note. No extraneous 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?

Covers purpose and key behavior, but omits return value, error conditions, and permission requirements. For a simple setter with no output schema, this is adequate but not fully complete.

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%, but description adds meaning: offset is 'minutes after adhan' and prayer is 'for a prayer'. This clarifies parameter purpose. Missing allowed values or range for offset_minutes and prayer names.

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: 'Update the Iqama offset' specifies the action and target. Distinguishes from sibling get_iqama_time by indicating a write operation.

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?

Describes transient nature of changes ('in-memory only, resets on restart'), which is useful context. However, no explicit guidance on when to use vs alternatives like get_iqama_time.

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