get_moon_info

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

With no annotations, the description carries full burden and adds value by describing the return structure (dict with 'data' and '_meta' keys, including illumination, phase_name, age_days, etc.). It does not mention side effects, but for a read-only query tool, this is acceptable. The return details increase transparency.

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 brief, well-structured with Args and Returns sections, and contains no redundant sentences. Every line serves a purpose, making it efficient for an AI agent to parse.

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 (2 parameters, no annotations, no output schema provided), the description is largely complete. It covers purpose, parameters, and return structure. Minor gaps: usage guidelines and full list of return fields are missing, but the output schema (though not shown) may fill the latter.

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 schema provides only types with no descriptions (0% coverage). The description compensates fully by specifying format for 'time' ('YYYY-MM-DD HH:MM:SS') and type for 'time_zone' ('IANA timezone string'), significantly aiding correct parameter usage.

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 first sentence clearly states the tool's purpose: 'Get detailed information about the Moon's phase and position.' This distinguishes it from siblings like get_celestial_pos, which covers general celestial positions, and get_constellation, which focuses on constellations.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or context for choosing get_moon_info over other sibling tools.

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