get_moon_info

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

Discloses that providing lat/lon enhances output with local altitude/azimuth, and specifies return dict structure. Without annotations, this provides adequate behavioral context, though no mention of error conditions or rate limits.

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 separate sections for intro, parameter explanations, and return info. Slightly verbose in places but overall efficient and front-loaded with purpose.

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?

Covers all key aspects: purpose, parameters, optional behavior, and return structure. With output schema present, the description is sufficiently complete for a tool with moderate 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?

With 0% schema coverage, description fully compensates by providing format (YYYY-MM-DD HH:MM:SS), type (IANA timezone), purpose (observer lat/lon for local position), and optionality. Adds meaning well 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 verb 'Get' and resource 'detailed information about the Moon's phase and position', distinguishing it from sibling tools like get_celestial_pos which cover other celestial bodies.

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?

Implies use when moon data is needed, but does not explicitly contrast with alternatives (e.g., get_celestial_rise_set for rise/set times, list_visible_planets for planets). No 'when not to use' guidance.

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