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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description usefully adds the endpoint, required fields, and a concrete cost (10 credits, Tier 1), which is real value beyond annotations, but it says nothing about what the four cycles/age boundaries look like or any auth/rate considerations.

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?

Front-loads the core purpose in one sentence, then uses compact bracketed metadata for group, endpoint, required inputs, and cost. No wasted prose, though the bracketed block is boilerplate rather than explanation.

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?

With an output schema present, return values need not be explained, and annotations cover the safety profile. The description supplies system, endpoint, required fields, and cost, but omits any differentiation from the near-identical non-strict kabbalistic 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 coverage is 50%: 'fields' and 'precision' are documented in the schema, while 'date' and 'name' carry only pattern/length constraints. The description merely restates '[Required: name, date]', which the schema already encodes, so it adds no new parameter meaning.

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?

States a specific verb ('Calculate'), resource ('four Pinnacle cycles with their age boundaries'), and system ('Kabbalistic (Mathers strict)'). This distinguishes it from the Chaldean/Pythagorean/Vedic pinnacle siblings, though it never explicitly contrasts with the non-strict 'astroway_numerology_kabbalistic_pinnacles' variant that sits right next to it.

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?

The description gives no when-to-use guidance and names no alternatives among the many pinnacle siblings. It states only required inputs and cost, leaving the agent to infer when this system is preferable to the other four pinnacle variants.

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