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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety behavior is covered by structured data. The description adds only a billing detail (10 credits, Tier 1) and the tradition group, which is mildly useful but says nothing about what the analysis returns, its dependencies, or any rate/credit implications beyond the tag.

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?

It is short and front-loaded, but it is under-specified rather than concise: two fragments that convey no actionable content. Brevity here reflects missing information, not disciplined editing.

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 described, but for a 15-parameter, 4-required analysis tool the description omits purpose, usage conditions, and any differentiation from its many siblings. The group and cost tags are the only context supplied.

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 must compensate for undocumented inputs such as city, date, time, latitude, longitude, cosmogram, zodiacType and houseSystem — and it provides nothing. A caller must infer all of these from the schema alone, and several have no schema description at all.

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 is a tautology: it restates the title 'Qualities & Quantities' as 'Qualitative + quantitative analysis' without naming a verb, resource, or what is actually computed. It does not distinguish this tool from the near-identical sibling astroway_hels_qualities_and_quantities or from other Schmidt-tradition siblings such as astroway_hellenistic_schmidt_aspectual_typology. Only the group/cost tags carry any identifying information.

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 when-to-use, when-not-to-use, or alternative-tool guidance anywhere in the description. An agent cannot tell from this text why it would pick this tool over the duplicate 'hels' variant or the many other hellenistic_schmidt_* tools.

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