get_eid_dates

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

No annotations are provided. The description is minimal and does not disclose any behavioral traits such as error handling for invalid years, data source, or response format. It does not add context beyond the basic action.

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 sentence with no unnecessary words. It is efficiently front-loaded and every part contributes value.

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 the tool's simplicity (one parameter, no output schema), the description is fairly complete. It states input and output. However, it could mention date format or invalid year behavior, but it's adequate for the complexity.

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?

The only parameter 'gregorian_year' has a schema title 'Gregorian Year' but description adds meaning by specifying it is the year for which to return Eid dates. With 0% schema description coverage, this compensation is helpful.

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 it returns Gregorian dates for two specific Eids given a year. The verb 'Return' and resource 'dates of Eid al-Fitr and Eid al-Adha' are specific and distinguish it from sibling tools like get_hijri_date or get_islamic_events.

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 usage for getting Eid dates, but it does not explicitly state when to use this tool versus alternatives or provide any exclusions. No guidance on prerequisites or limitations.

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