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

Annotations already declare the full safety profile (readOnlyHint, idempotentHint, non-destructive, closed-world), so the bar is lower. The description usefully adds the billing trait (10 credits, Tier 1) and the endpoint, which are real behavioral context an agent cannot get from annotations. It adds nothing about latency, auth, or what the result contains, but no contradiction exists with POST + readOnlyHint.

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 single content sentence is front-loaded and waste-free, but the remaining four bracketed tag lines are metadata fragments (group, endpoint, required, cost) rather than prose, making the definition feel like a stub. Nothing is verbose, yet the brevity is under-specification rather than disciplined conciseness.

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?

This is a high-complexity tool: three nested birth-data objects with timezone, ayanamsa, house-system and precision options. Output schema exists so return values need not be explained, but the description never says what a genogram computes or how the three generations relate, leaving an agent guessing about the tool's actual output intent.

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%, including rich nested per-field docs (tz handling, houseSystem letters, rejected short forms), so the schema does the heavy lifting and baseline is 3. The description only restates the three required parameter names, adding no new semantics for grandparent/parent/child, fields, or precision.

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?

"Multi-generational family pattern map" names a resource but no verb — it does not say whether it computes charts, draws a diagram, or interprets patterns. It is also not distinguished from close siblings such as astroway_family_system_pattern, astroway_family_parent_child_deep, or astroway_family_sibling_dynamics. Purpose is inferable but vague.

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, despite four sibling family tools that overlap conceptually. The bracketed [Required: grandparent, parent, child] is input requirements, not usage routing, and duplicates the schema's required array.

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