get_yearly_islamic_events

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

With no annotations, the description carries full burden. It discloses that the tool filters to a single year and discards overhead arrays, implying efficient single-year queries. However, it does not mention other behaviors like data source, accuracy, or any 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?

Two concise sentences front-load the purpose and add a behavioral note. No fluff or redundancy; every sentence earns its place.

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 description omits key context: what constitutes 'significant Islamic calendar milestones,' how location parameters affect results, and the return format. Given four parameters and no output schema, the description is notably incomplete.

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%, so description must compensate. It only references target_year (via default 2026), but ignores location_name, latitude, and longitude. The purpose of these location parameters is unexplained, leaving a significant gap.

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 tool retrieves significant Islamic calendar milestones filtered to a target year, with a default of 2026. This is specific and distinct from sibling tools like find_nearest_mosques and get_monthly_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?

The description does not explicitly state when to use this tool vs alternatives, but the sibling tools cover different domains (mosques and prayer times), implying usage context. The mention of discarding multi-year arrays hints at efficiency for yearly queries, but no direct guidance.

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