get_yearly_islamic_events

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

With no annotations provided, the description carries full burden. It discloses the default-year behavior but fails to mention that location parameters (location_name, latitude, longitude) could affect the events returned. No disclosure on permissions or response structure.

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 sentences with no fluff. Every word serves a purpose. The default-behavior detail is well placed.

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?

Given 0 required parameters and existing output schema, the description is minimally adequate. But it omits explanation of location parameters and the nature of 'milestones,' which would be helpful for a complete understanding.

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%, but the description only adds default value info for target_year. It does not explain the purpose or effect of location_name, latitude, or longitude, leaving their meaning ambiguous.

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 for a target year' and mentions defaulting to current year. This specific verb+resource structure distinguishes it 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 notes defaulting to current year, providing some usage context, but does not explicitly state when to use this tool over alternatives or when not to use it. Since siblings are clearly different, the implication is sufficient but not explicit.

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