get_weekly_prayer_times

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

No annotations are provided, so the description bears full responsibility. It only states the basic operation without disclosing return format, timezone handling, date boundaries (e.g., start from today or next day), or city matching 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?

Single sentence with no waste. The essential elements (action, resource, scope, constraint) are front-loaded.

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 simple 1-parameter tool, the description covers the core purpose and constraint. However, missing details like return format, timezone, and date range definition leave the agent uncertain about the exact output.

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 100%, providing a baseline of 3. The description adds the 'Moroccan city' constraint, clarifying the allowed values beyond the schema's generic 'City name'. However, it omits listing supported cities or referencing list_prayer_cities.

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 'Get', the resource 'prayer times', the temporal scope 'next 7 days', and the geographic constraint 'Moroccan city'. This distinguishes it from siblings like get_prayer_times (general date) and get_next_prayer (single prayer).

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?

No guidance on when to use this tool versus alternatives like get_prayer_times for a specific date. The description does not provide usage context or mention sibling tools for broader or narrower queries.

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