Astronomy Lookup

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

Annotations already indicate read-only, non-destructive, idempotent, and open-world. The description adds specific behavioral details: it returns multiple astronomy metrics, accepts past/future dates, defaults today. No contradictions.

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, no fluff. Front-loaded with the return data types, then location and date requirements. 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?

Despite no output schema, the description enumerates the return fields (sunrise/sunset, moon phase, etc.). With 8 parameters and 0 required, it provides enough context for an AI to invoke correctly.

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 100%, so baseline 3. The description adds crucial usage rules: 'Provide one of: ip, location, or lat+long. At least one is required.' This mutual exclusivity and requirement are not explicit in the schema, adding significant value.

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 retrieves astronomy data (sunrise/sunset, moon phase, etc.) for a location and date. This distinguishes it from all sibling tools, which are primarily about currency, DNS, weather, or IP geolocation.

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 specifies the three ways to provide location (ip, location, or lat+long) and the date format. It lacks explicit when-not-to-use guidance but is clear enough for an AI to select correctly.

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