ephemeris_next_eclipse

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

Discloses behavior beyond readOnlyHint: returns global or local results based on location, mentions credit cost, and specifies output details (magnitude, duration). No contradiction with annotations.

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?

Well-structured with headings, bullet points, and examples. Every sentence adds value; no wasted words. Front-loaded with core purpose, then organized details.

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?

Complete for a query tool: covers purpose, parameters, optional behavior, output summary, and credit cost. No output schema needed as description explains return values. All essential information for correct invocation is present.

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 has 100% coverage with good descriptions, but description adds value by explaining the optional location behavior and providing usage context (e.g., 'WITH latitude+longitude → returns local contact times'). Enhances understanding beyond schema.

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?

Clearly states 'Find the next solar or lunar eclipse' with specific return fields (eclipse type, date/time, magnitude, duration). Distinguishes from many sibling ephemeris tools by being uniquely focused on next eclipse.

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?

Provides explicit when-to-use guidance: with location (local visibility) vs without (global). Includes example queries (e.g., 'When is the next solar eclipse?') and three concrete examples with different inputs, making usage clear.

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