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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so safety is covered. The description adds genuinely useful operational context the annotations do not: the endpoint, the four required inputs, and the 10-credit Tier 1 cost, which matters for an agent budgeting calls.

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 metadata block is compact and scannable, and nothing is redundant. However, the leading sentence is the least informative part of the definition and should have been the substantive one, so the structure is efficient but poorly front-loaded.

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, but a 15-parameter chart-based tool with a cryptic one-line purpose and no explanation of the optional tuning parameters leaves an agent unable to call it with confidence or know when it is the right choice.

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 coverage is only 33% across 15 parameters, so the description needs to compensate, and it does not. It lists the four required fields but says nothing about the eleven optional ones such as ayanamsa, zodiacType, houseSystem, fields, precision, or timezone, several of which have no schema description at all.

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 only descriptive sentence, "Trine elemental partners with natural synergy," is a fragment of astrological reasoning rather than a statement of what the tool computes. The reader must infer from the title and endpoint that it derives ideal business-partner signs from a birth chart, and nothing distinguishes it from sibling astroway_business_team_compatibility.

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 [Group: Business Astrology] tag implies business context, but there is no explicit when-to-use guidance, no prerequisite statement, and no routing to alternatives such as astroway_business_team_compatibility, astroway_relational_synastry, or astroway_horoscope_compatibility.

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