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 safety is covered. The description adds genuinely useful non-schema context: the endpoint path and the billing tier ('Cost: 10 credits (Tier 1)'). It says nothing about latency, rate limits, or what the response contains beyond the implied compatibility framing.

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 bracketed metadata block is compact and front-loads the endpoint, required params, and cost efficiently. However, the leading sentence is cryptic astrological shorthand that consumes space without conveying actionable meaning, so the structure is tidy but the content is thin.

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, 10-credit tool with an output schema, the definition omits what the tool actually returns (which signs, in what ordering/format), any prerequisite birth-data requirements beyond the bare names, and how it differs from adjacent business and compatibility tools. An output schema excuses explaining return values, but not the near-total absence of purpose and routing guidance.

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 only 33% across 15 parameters, so the description is expected to compensate, but it only restates the four required names (date, time, latitude, longitude) that the schema's `required` array already declares. It adds no meaning for the eleven optional parameters such as ayanamsa, houseSystem, precision, or fields.

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 line 'Trine elemental partners with natural synergy' gestures at the output (partner signs grouped by trine elements) but never states a verb or what is actually computed from the birth data. The [Endpoint: POST /v1/business/ideal-partner-sign] tag and group label supply the only concrete framing. An agent can guess the topic but not the 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 statement and no comparison against the many plausible siblings (astroway_business_team_compatibility, astroway_business_founder_personality, astroway_vedic_compatibility_ashtakoot, astroway_relational_match_score). The description only lists required inputs and cost, which does not tell the agent when this tool is the right choice.

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