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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds cost ('50 credits (Tier 3)') and group metadata, which is useful behavioral context for budgeting calls, but it says nothing about the calculation's inputs/outputs beyond the converse flag.

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 plus bracketed metadata tags; the core purpose is front-loaded and nothing is padded. The cost/group tags are structured rather than prose waste.

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 a rich, fully documented input schema, an output schema, and complete safety annotations, the description only needs to identify the technique and its distinctive option. It does that, though the parenthetical definition of minor progressions is thin for an agent unfamiliar with the technique.

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 100%, so the schema fully documents body, fields and precision, including targetDate, targetTime and targetTzOffset. The description's mention of 'a target date' and 'converse direction' only loosely mirrors two nested parameters and adds no format or default detail beyond the schema.

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?

Names a specific verb and resource ('Calculate minor progressions') and defines the technique via the parenthetical '(lunar month-for-a-year)', which is genuinely informative for an astrologer. However, it does not differentiate itself from the many sibling progression/direction tools (progressions, tertiary_progressions, symbolic_directions), so an agent still has to infer which technique applies.

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 and no mention of alternatives among the crowded prognostics siblings. 'Supports converse direction' is a capability note rather than routing guidance, so the agent gets no help deciding between minor progressions and progressions/tertiary_progressions.

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