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 is covered. The description adds genuinely useful non-schema context: the billing cost (10 credits, Tier 1) and the tradition group, but says nothing about return shape or any computational caveats.

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 text is short, front-loaded with the defining phrase, and the bracketed metadata lines are easy to scan. It is arguably too sparse for a 15-parameter tool, but as raw conciseness and structure it is efficient with no wasted 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 with 15 parameters, three enums, and only 33% schema description coverage, the definition leaves the agent without enough context to invoke it confidently or to tell it apart from its dodekatemoria sibling.

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?

Schema description coverage is only 33% across 15 parameters, so the schema does not carry the load and the description offers no parameter meaning at all. Nothing is said about how date/time/latitude/longitude interact, nor about the ayanamsa/zodiacType/houseSystem options that materially change output, leaving a significant compensation 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 identifies the technique ('2.5° micro-sign per planet') and its tradition group, which gives a rough sense of what the tool computes. However it uses a cryptic technical label with no verb/resource framing (e.g. 'computes the duodecima placements for a chart'), and it does not distinguish itself from the near-identical sibling astroway_hellenistic_greenbaum_dodekatemoria, which uses the same 2.5° twelfth-part division.

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 guidance on when to use this tool, what prerequisites it has, or how it relates to alternative Hellenistic division tools. The 'Group' and 'Cost' tags are metadata, not usage direction, so an agent must infer the trigger condition from the name alone.

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