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

Annotations already declare readOnly=true, idempotent=true, destructive=false, openWorld=false, so the safety profile is covered. The description adds genuinely new context: the POST endpoint, the 10-credit Tier 1 cost, and the required-input set, which is useful for planning calls. It does not, however, describe what computation or behavioral edge cases (e.g. sidereal vs tropical requirements) apply.

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?

Compact and front-loaded with the concept, followed by tight bracketed metadata (group, endpoint, required, cost) and the alias note. Nearly every line carries information, though the opening phrase is too vague to be the headline.

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?

Output schema and annotations are present, so return values and safety need not be restated. Still, for a 15-parameter computational chart tool the description leaves the agent guessing about the doctrinal/psychological framing and which optional inputs matter, making it only minimally complete.

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 only 33% across 15 parameters, so the description should compensate; instead it merely restates the four required fields already marked required in the schema. No meaning is added for the many undocumented options (zodiacType, houseSystem, cosmogram, name, city, etc.) that an agent would need to select correctly.

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 line 'Saturn-as-shadow integration work' identifies the subject (Liz Greene's Saturn shadow concept) but is a vague noun phrase without a clear verb or output, and it does not distinguish this from its psyg siblings (archetypal_figures, individuation_path, lunar_myth, parental_imagos). The Endpoint and Group tags help place it within the Modern Psychological family but not the specific work performed.

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 states required inputs (date, time, latitude, longitude), the endpoint, and the cost, but gives no guidance on when to choose this tool over the sibling Greene/psyg psychological tools or what use case it serves. No alternatives or exclusions are named.

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