Get planet meaning details - Complete astrology planet interpretation

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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful context about the returned content fields and identifier flexibility, but it does not disclose additional behavioral traits such as error behavior, rate limits, or data source caveats.

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 front-loaded with the action and the required id semantics, then enumerates the response fields and use cases. It is somewhat dense but every sentence contributes useful information, with no significant filler.

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 annotations, full schema documentation, and presence of an output schema, the description provides all necessary orientation: what the tool does, what inputs are expected, what data is returned, and common use cases. Nothing essential for correct invocation is missing.

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 description coverage is 100%, with detailed descriptions for id, lang, and compact already present. The description mostly restates the id flexibility (lowercase vs case-insensitive names) and does not add substantial meaning beyond the 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?

The description clearly states a specific action ('Retrieve comprehensive planet interpretation') and a specific resource ('any astrological planet'), and it explains the required identifier style. It is easy to distinguish from the sibling list tool because it describes a per-planet ID lookup by name and ID.

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?

The description gives explicit use cases such as birth chart readings, natal chart interpretation, transit meanings, and planet meaning lookups, which clearly indicate when this tool is appropriate. It does not explicitly name an alternative or exclusion case, but the context is strong enough to guide selection.

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