Get Planet Position

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

Annotations (readOnly, idempotent, non-destructive) are consistent. Description adds behavioral details: geocentric ecliptic coordinate system, defaulting datetime to now, timezone handling, and supported bodies.

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?

First sentence states the core purpose, followed by return values, usage comparison, body list, and examples. No redundant sentences; all content 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?

Given the output schema exists, the description covers all necessary aspects: purpose, usage guidance, parameter behavior, and examples. No gaps for this single-body, single-moment 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 coverage is 100%, but description adds value with examples showing parameter usage (e.g., leaving datetime empty, combining with timezone). The default behavior for datetime and the meaning of 'zodiac' options are clarified.

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 computes the zodiac position of a single body/point at a single moment, listing return fields. It explicitly distinguishes from siblings ('rather than a full chart').

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 guidance: 'Use for "where is X" questions rather than a full chart.' Includes three examples covering common scenarios, though no explicit when-not-to-use statements.

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