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. The description adds genuinely useful non-schema context: the billing cost (10 credits, Tier 1) and the doctrinal group (Hellenistic: Schmidt tradition). It does not describe required chart inputs or output characteristics, so it only partially extends the annotations.

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?

Three short lines, front-loaded with the doctrinal subject, followed by structured group/cost metadata and the alias note. Nothing is padded and each line carries distinct information (identity, cost, alias), though the metadata uses bracketed conventions rather than natural prose.

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?

An output schema exists, so return values need not be explained, but this is a 15-parameter chart-calculation tool with 33% parameter coverage and no usage or input context. The description never signals that a birth moment and coordinates are required or how the various doctrinal options affect results, leaving the agent under-informed for such a complex call.

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?

With 15 parameters and only 33% schema description coverage, the description is expected to compensate and adds nothing about any parameter. Key inputs (date, time, latitude, longitude required; zodiacType, houseSystem, cosmogram) are left to the schema alone, and the description never explains how this tool's doctrine depends on ayanamsa or zodiacType. It provides zero parameter 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?

"Stoic doctrine of elemental natures" is a subject label rather than a verb+resource statement; it essentially restates the title "Stoic Elementhood" without saying what the tool computes or returns. The alias note identifies it as equivalent to astroway_hellenistic_schmidt_stoic_elementhood, which helps routing slightly, but nothing states the operation performed. Tautological against the name/title, so a 2.

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 when-to-use, when-not-to-use, or alternative selection guidance is given. The parenthetical alias note is the only routing hint, telling the agent it is interchangeable with the full-name variant, but that is identity information, not usage context. No prerequisites or scenario guidance is present.

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