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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive, so the safety profile is covered. The description does add genuinely useful behavioral context the annotations cannot convey: the tradition grouping (Hellenistic: Greenbaum) and the cost (10 credits, Tier 1). It says nothing about what the computation requires or returns, but an output schema exists.

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 entry is short and front-loads the technique name, and the group/cost tags carry real routing value. However, the brevity is under-specification rather than efficiency for a 15-parameter tool, leaving the definition thin.

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?

For a fairly complex chart-computation tool, the description omits what dodekatemoria are, what input chart is expected, how it relates to the duodecima/decans siblings, and any cost or latency expectations beyond the credit tag. An agent cannot confidently select it over the many neighboring Hellenistic tools.

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, several fields (city, name, cosmogram, zodiacType, houseSystem, ayanamsaId, latitude, longitude) are undocumented anywhere. The description adds no parameter meaning whatsoever, so it fails to compensate for the coverage 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 text 'Dodecatemoria sub-divisions of zodiac' essentially restates the title with a thin gloss and never states what the tool does (compute and return dodekatemoria placements for a chart). It also fails to differentiate from the near-duplicate sibling astroway_hellenistic_greenbaum_duodecima, which names the same 12th-part technique.

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 guidance, no prerequisite statement (e.g. that a birth date/time/place drives the computation), and no pointer to alternatives such as the duodecima or zodiacal_decans tools. The agent must infer everything from the name.

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