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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds genuinely useful non-schema context: the 10-credit Tier 1 cost and the fact that this is a cursor-friendly alias for the canonical tool. It says nothing, however, about what the map contains or how it is computed.

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?

It is short and front-loads the purpose line, but the brevity reflects under-specification rather than tight editing — the group, cost, and alias tags are metadata fragments rather than substantive guidance. Nothing is wasted, but very little is said.

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?

For a 15-parameter chart tool with only 33% parameter coverage, the description is far too thin: no statement of what the compatibility map contains, no guidance on required birth data, and no differentiation from sibling element tools. The existence of an output schema excuses it from describing return values, but the input-side and purpose-side gaps remain.

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?

With 15 parameters and only 33% schema description coverage, the description carries a heavy burden and contributes nothing — no mention of date, time, latitude/longitude, zodiac type, ayanamsa, or house system semantics. The undocumented parameters (city, date, name, time, cosmogram, zodiacType, houseSystem, ayanamsaId, latitude, longitude) are left to bare types and enums, which the description does not compensate for.

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 resource ('relational element compatibility map') but as a bare noun phrase with no verb, so what the tool actually computes is left implicit. It does not distinguish itself from the many closely named siblings (element_balance, element_integration, cycle_of_becoming), all of which are 'Modern Psychological' tools. A reader can guess the domain but not the specific operation.

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 mention of alternatives among the element/relational siblings. The only context given is the group tag and credit cost, which is billing metadata rather than usage guidance.

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