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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the billing attribute (10 credits, Tier 1), which is a genuine non-annotation behavior but is thin; it says nothing about what the computation returns, whether it is per-sign or per-planet, or any limits.

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?

Two short lines, zero filler, with the subject line front-loaded ahead of the metadata tags. It is efficiently sized; the sparseness is a completeness problem rather than a verbosity problem.

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 specialized Hellenistic technique reachable among hundreds of sibling tools the definition supplies no domain framing, no usage context, and no distinction across the brennan/greenbaum/hand variants of the same material. An agent has almost nothing to route or disambiguate with.

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 it contributes nothing about any parameter. The four required params (date, time, latitude, longitude) are self-evident by name, but the many sidereal/house-system/zodiacType modifiers that materially change this specific output are left entirely to 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?

The phrase 'Ptolemaic Egyptian bounds rulers' identifies the astrological resource (term/bound rulers in the Egyptian tradition), which is a real domain object and not a tautology of the name. However it is a bare noun fragment with no verb, and it never distinguishes itself from the many sibling Hellenistic traditions (brennan, greenbaum, schmidt) that produce overlapping time-lord and ruler material, so an agent cannot tell why this one versus another without opening the schema.

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, prerequisite, or alternative-tool guidance anywhere in the description. The sibling set contains dozens of closely related Hellenistic ruler tools and the description gives no signal for choosing among them; only the '[Group: ...]' tag hints at a family, and that tag is shared by nine other tools.

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