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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds a genuinely useful behavioral fact (10 credits, Tier 1 cost), but says nothing about what 'deep' entails, response shape, or whether both charts must have exact birth times.

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 front-loaded sentence plus two bracketed metadata lines; nothing is padded or buried. It is terse to the point of being sparse, but every line earns its place.

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 rich. However, for a two-chart, 10-credit analysis the description omits what distinguishes it from sibling family tools and any indication of the scope of the result, leaving it minimally complete.

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 parent/child objects are documented in detail (date/time formats, coordinates, houseSystem letters, timezone handling), so the schema carries the load. The description adds no parameter meaning of its own, so the baseline 3 applies.

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 pairing and technique (parent-child synastry), which is more than the bare name conveys, but 'Deep ... analysis' largely restates the title 'Parent-Child Deep'. It never distinguishes this from the many adjacent family/relational tools, so the boundary is left to the reader.

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, no prerequisites, and no naming of alternatives such as astroway_family_system_pattern, astroway_family_genogram, or astroway_relational_synastry. The only routing hint is the '[Group: Family Astrology]' tag, which is implied usage at best.

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