Joys of Planets

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

Annotations already indicate readOnlyHint=true and destructibleHint=false. The description adds nothing beyond what is already in atrunctions, failing to disclose any behavioral aspects like side effects, input constraints, or output structure.

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 extremely short, but this brevity sacrifices clarity and completeness. It is not well-structured; it reads as a fragment rather than a coherent explanation.

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 complexity (11 parameters, no output schema) and the large set of sibling tools, the description fails to convey essential context, such as what 'planetary joys' means, what the tool computes, or how to use it.

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 input schema has 11 parameters with 0% description coverage. The description does not explain any parameter, not even the required 'date' and 'time'. The example request body shows a chart field but lacks explanation.

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 mentions 'Classical planetary joys (Sun-Leo-9th, etc.)' and groups it by tradition, but does not explicitly state the tool's action (e.g., 'computes' or 'returns'). The purpose is vague and could apply to multiple tools.

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 its many siblings (e.g., 'hellenistic_brennan_bonifications_maltreatments'). There is no mention of prerequisites or typical use cases.

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