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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds that the default moment is 'now' and that the KP sub-lord chain is included, which is useful context, but says nothing about credit cost behavior beyond the tag, output shape, or limits. With annotations doing the heavy lifting, a 3 is appropriate.

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 tight sentences with the core scope and use case front-loaded; nothing is padded. The bracketed Group/Cost lines are metadata rather than prose, but they add little clutter.

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, and annotations cover safety. However, for an 8-parameter tool with sub-hour timezone semantics and a large sibling set, the description omits guidance on ayanamsa selection, timezone vs offset, and when to prefer this over other KP transit 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?

The description refers to a parameter named `targetDate`, but the schema defines `date`/`time` and no `targetDate` at all, which risks misleading the agent about the required input name. It adds no meaning for ayanamsa, precision, fields, or timezone, which is significant given only 63% schema description coverage.

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 names a specific resource and scope: sidereal positions of all 9 grahas (including Ketu) with the KP sub-lord chain attached, plus the intended use case ('KP transit-timing'). This clearly separates it from generic transit tools, though it does not distinguish it from close KP siblings such as astroway_vedic_kp_sub_lords or astroway_vedic_kp_cusps.

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?

'Use for KP transit-timing' gives an implied context for invocation, but there is no when-not guidance and no named alternative among the many sibling tools. In a catalog this size, the absence of routing language against the other KP and prognostics transit tools is a real gap.

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