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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds genuinely new behavioral context the annotations lack: the 500-credit Tier 6 cost and the explicit instruction to confirm with the user first, which materially changes invocation behavior.

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?

One sentence of purpose followed by structured Group/Cost metadata; the core meaning and the cost caution are front-loaded with no wasted prose. The cost block is repetitive but serves a routing function.

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 no explanation, and the cost/confirmation guidance is present. Still missing for a complex 8-parameter, nested-object tool: what the search window knobs do and how the result is shaped (e.g. a narrowed time window with confidence).

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 only 38% across 8 parameters, so the description must compensate and largely does not. It hints at 'life events' and 'transit/direction hits' but never explains orb, stepMinutes, searchRangeMinutes, the primary/symbolic/progression method toggles, precision or fields.

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?

Specific verb (rectify) plus resource (birth time) and the inputs that drive it (life events, transit/direction hits), so the tool's function is unmistakable. It does not, however, distinguish itself from the close sibling astroway_prognostics_rectification_trutine, which an agent would need to choose between.

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?

Usage is implied by 'Rectify an approximate birth time', and the cost line adds an actionable procedural rule ('confirm with user before invoking'). But there is no explicit when-to-use versus the other rectification tool or when rectification is premature (e.g. no events supplied).

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