get_current_sky

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

With no annotations, the description bears full transparency burden. It mentions output includes positions in houses and aspects, but does not disclose side effects, authentication needs, rate limits, or data format. This is adequate but not thorough.

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?

A single, clear, concise sentence that front-loads the tool's purpose and output details. Every word is necessary and well-structured.

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 params, no output schema) and sibling context, the description adequately covers function and output. Minor omission: no mention of time resolution or time zone, but acceptable for a 'current' sky tool.

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 descriptions already fully define latitude and longitude (decimal degrees, ranges, sign conventions) with 100% coverage. The tool description adds no additional parameter meaning beyond what the schema provides, earning the baseline score.

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 the tool returns the current sky (transits) for a given location, including house positions and aspects. It distinguishes from sibling tools like 'get_transits' (likely for arbitrary dates) and 'get_planet_positions' (without aspects/houses).

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 explicit guidance on when to use this tool versus alternatives. The phrase 'instant présent' implies it's for current sky only, but does not mention exclusions (e.g., past/future dates) or refer to sibling tools like 'get_transits' for other times.

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