get_eid_dates

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

No annotations are provided, so the description carries the full burden. It discloses the read-only nature via 'Return' and names both Eid dates, but it does not mention any constraints (e.g., valid year range), calculation method, or return format. This is adequate but not rich for a tool with no annotation support.

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, direct sentence with no filler: 'Return the Gregorian dates of Eid al-Fitr and Eid al-Adha for a given year.' Every word contributes to the meaning, making it concise and well-structured.

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 (one parameter, no output schema, no annotations), and the description covers the core function completely. However, since there is no output schema, it would be marginally better to state the structure of the returned dates (e.g., object with keys for the two Eids). Still, the low complexity makes this a minor gap.

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 for the parameter. It only says 'for a given year,' which essentially restates the schema's property name 'gregorian_year' and title 'Gregorian Year'. It adds no extra meaning about acceptable values, format, or behavior.

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's function: returning the Gregorian dates of Eid al-Fitr and Eid al-Adha for a given year. The specific verb 'Return' and the explicit resource (the two Eids' dates) distinguish it from sibling tools like get_islamic_events or get_ramadan_dates, which have broader or different scopes.

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 implies when to use the tool: when you need the Gregorian dates of the two major Islamic holidays for a specific year. It doesn't explicitly mention alternatives or exclusions, but the context is clear enough for an agent to select it appropriately among the sibling calendar tools.

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