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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds the cost ('10 credits (Tier 1)') and the endpoint, which is genuine value beyond the schema, but it says nothing about auth, latency, or output shape.

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 definition is short and front-loaded: the archetype description leads, followed by compact bracketed metadata. Almost every line carries information, though the endpoint tag is of limited use to an agent selecting the tool.

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?

With 15 parameters, three enum families, and low schema description coverage, the description is too thin to guide correct invocation. The presence of an output schema excuses it from describing return values, but the failure to explain the numerous optional astrological parameters leaves a real gap.

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?

Only 33% of the 15 parameters have schema descriptions, and the description merely repeats the four required fields already enumerated in the schema's required array. It adds no meaning for the optional parameters (city, name, cosmogram, zodiacType, houseSystem, latitude/longitude semantics) that the agent must reason about, so it fails to compensate for the coverage gap.

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 names a concrete output ('concise leadership archetype + key strengths'), which is more specific than a bare resource name and tells the agent what it will get back. However it does not differentiate itself from close siblings like astroway_business_founder_personality, astroway_business_marketing_style, or astroway_business_risk_profile, so an agent must infer the boundary rather than being told it.

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?

There is no statement of when to choose this tool over the related business tools, nor any exclusion criteria. The '[Required: date, time, latitude, longitude]' tag gives prerequisites but not usage context, and no alternate tool is named.

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