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

Annotations already declare readOnlyHint, openWorldHint, destructiveHint=false, so the safety profile is covered. The description adds genuinely useful operating context the annotations cannot: a 100-credit Tier 4 cost, the endpoint, and group membership. It stops short of noting that idempotentHint is false (repeated calls may re-charge), which would have been valuable for a paid tool.

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?

The core sentence is front-loaded and wastes nothing; the tagged metadata lines (group, endpoint, cost) are compact and each carries distinct information rather than padding. Nothing is redundant.

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 explained, and the input schema is self-documenting. What remains missing for an agent choosing between many near-identical AI-interpretation siblings is disambiguation guidance, especially against astroway_mcp_ai_explain_transit.

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% and the nested body, fields, and precision parameters are all thoroughly documented in the schema itself. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the heavy lifting.

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 states a specific verb and resource — AI interpretation of current/upcoming transits to a natal chart — with the added scope 'what each major transit means in life context'. This separates it from natal-, synastry-, placement-, and tarot-focused siblings reasonably well. It does not, however, differentiate itself from astroway_mcp_ai_explain_transit, which sounds like it operates in the same territory.

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 phrase 'current/upcoming transits to a natal chart' implies the usage context, but there is no explicit when-to-use statement, no prerequisites (e.g. that a natal chart is needed as input), and no routing to or away from the near-twin sibling astroway_mcp_ai_explain_transit. Usage is left to inference.

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