get_islamic_events

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

No annotations are present, so the description must convey safety and behavior. It implies a read-only operation by using 'Return', but does not disclose the return format, whether the year parameter has bounds, or what constitutes a 'named event'. The month range (1–12) is useful, but other behavioral details are omitted.

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 a single, front-loaded sentence that states the main action and optional filter with no filler. Every word serves a purpose.

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?

The tool is simple with 2 parameters and no output schema or annotations. The description covers the core functionality and month filter, but it lacks details like return values, examples, or edge-case behavior. It is adequate as a minimal viable description but has room for improvement.

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 description coverage is 0%, so the description must compensate. It adds the month range (1–12) and clarifies the filter is optional, which the schema only partially conveys via null default. However, it does not explain hijri_year's format, valid range, or semantics beyond the name.

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 ('Return') and resource ('named Islamic events for a Hijri year'), clearly differentiating from siblings that target specific event types like Ramadan or Eid. The optional month filter is also mentioned, making the tool's scope 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?

No guidance on when to use this vs alternatives. It doesn't mention exclusions or situations where a sibling tool would be preferable, such as get_ramadan_dates or get_eid_dates for specific events. Only provides the basic operation without context.

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