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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds genuinely useful non-schema context — a 10-credit Tier 1 cost and its Schmidt-tradition grouping — which matters for budget-aware tool selection. It still says nothing about what the call actually returns or how it behaves on edge inputs.

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-loads the one content line before the metadata tags, so nothing is padded. However, the brevity reflects under-specification rather than disciplined concision — the cost/group tags are the only actionable content.

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 the description still fails to convey what this niche technique produces or when it is relevant, and it is silent on all 15 inputs. For a domain-specific Hellenistic calculation, this leaves the agent guessing about applicability.

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 carries a real compensation burden, and it adds zero parameter information — not even which required inputs (date, time, latitude, longitude) drive the result or what 'elemental natures' maps to. The agent must read the schema entirely on its own for a complex 15-param call.

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 restates the title as a topic phrase — 'Stoic doctrine of elemental natures' — with no verb, no statement of what is computed, and no output mentioned. It does not distinguish this from near-identical siblings such as astroway_hels_stoic_elementhood or astroway_hellenistic_schmidt_sect_classes. It is essentially a topical label rather than a purpose statement.

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; the only additional lines are group and cost metadata. An agent cannot tell from this text whether to call this versus the other Schmidt-tradition or hellenistic tools for a given question.

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