التاريخ الهجري اليوم

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

With no annotations, the description carries the full burden. It usefully discloses that the conversion is computed locally with no network call, which is real behavioral context, but says nothing about the calendar convention used (e.g. Umm al-Qura), timezone handling, or the returned date format.

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?

One short sentence, front-loaded with the core action and the default/optional input, with the offline trait appended. Nothing is wasted.

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?

Adequate for a simple single-parameter read tool, but the absence of an output schema means the expected return shape and calendar convention are left undocumented. Some additional detail on the returned Hijri format would round it out.

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 parameter is fully documented in the schema, including its YYYY-MM-DD format and today-default. The description merely repeats the default, adding no syntax or format detail beyond the schema.

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?

States a specific verb and resource: it returns the Hijri date corresponding to today or a given Gregorian date. It is clearly distinguishable from Quran-audio/surah siblings, though it never names a sibling or contrasts with get_prayer_times.

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?

Implies usage by noting the default (today) and the optional explicit Gregorian input, which is enough to know when to call it. There is no explicit when-not guidance or reference to alternatives among the siblings.

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