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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety behavior is covered. The description adds genuinely useful context beyond that — the POST endpoint, the four required inputs, and the 10-credit (Tier 1) cost — but says nothing about what the calculation produces or any preconditions.

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?

Very short and cleanly front-loaded, with the bracket block giving a scannable structure and no filler sentences. However, the brevity crosses into under-specification rather than tight writing, so it is efficient without being informative.

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 15-parameter Hellenistic calculation with sidereal/house-system options and an output schema, an agent needs to know what is being computed and under which frame; the description supplies none of that. The existence of an output schema excuses it from describing return values, but it is still too thin for the tool's complexity.

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 coverage is only 33% across 15 parameters, so the description should compensate, but all it offers is '[Required: date, time, latitude, longitude]', which merely restates the schema's own required array. It adds no meaning for the eleven optional parameters (zodiacType, houseSystem, ayanamsa/ayanamsaId, precision, cosmogram, etc.).

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 tool name/title with a dictionary gloss; it contains no verb and never says what the tool actually computes or returns (e.g. dodekatemoria placements for a chart). It also does nothing to distinguish this from near-neighbor siblings like astroway_hellenistic_greenbaum_duodecima or astroway_helg_zodiacal_decans.

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?

No when-to-use statement and no named alternative or exclusion. The only context is the bracket metadata (group/endpoint/required/cost), which is operational plumbing rather than guidance about when this tool is the right choice over its several Hellenistic subdivisions siblings.

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