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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add provenance and data-quality behavior instead: times come from each masjid's own posted board, the read date is returned, and masjids lacking a current board are counted rather than estimated. That 'never estimated' disclosure is exactly the kind of behavioral trait annotations cannot express.

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?

A single sentence that front-loads what is returned, then appends provenance, freshness, and the no-estimation policy. Every clause carries distinct information and nothing is repeated from the title or schema.

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?

With one required parameter and no output schema, the description supplies the freshness signal (board read date) and coverage policy an agent needs to interpret results honestly. It stops short of saying what a result entry contains or whether masjids with no board still appear in the payload versus only in a count.

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% and the single city parameter is already documented with both name and path forms, so the schema does the heavy lifting. The description only adds the notion of city scope, not format or resolution behavior, so the baseline of 3 applies.

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 uses a specific verb-and-resource framing: today's iqamah (congregation) times for masjids in a city, and it glosses 'iqamah' so an agent can distinguish it from general prayer times. It never names the obvious alternative siblings (prayer_times, jumuah_times), so the differentiation is inferable rather than explicit.

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?

'Today's' implies the temporal scope, and the masjid-board framing implies this is the source for congregation start times rather than adhan times. However, there is no explicit statement of when to prefer this over prayer_times or jumuah_times, and no exclusions or prerequisites are given.

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