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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful operational facts: the POST endpoint, the four required inputs, and a 10-credit Tier 1 cost, which helps an agent budget calls. It stops short of saying what the map contains or how results are shaped, but the output schema covers returns.

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 definition is a tight, front-loaded label followed by a compact metadata block with zero filler. Every line is short and scannable, though the extreme brevity is what creates gaps elsewhere rather than crowding anything out.

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 astrological computation with several enums and a rich output schema, the description supplies no information about what the map contains or how the many sidereal/house-system options change the result. Annotations and the output schema carry safety and returns, but the agent is left to infer the tool's domain from the name alone.

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 must compensate, and it does not. It merely restates the four required params (date, time, latitude, longitude) that the schema already marks required, and says nothing about ayanamsa, zodiacType, houseSystem, fields, precision, or timezone semantics.

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 phrase 'Relational element compatibility map' names the resource but uses no verb and gives no scope beyond the tool name itself. It does not distinguish this tool from near-identical siblings such as astroway_psya_relational_element_map or astroway_relational_synastry_element_balance. An agent can guess it produces some compatibility/element output, but the purpose stays at the level of a label.

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 exclusions, and no routing to alternatives among the many relational and psychological siblings. The bracketed metadata states required inputs and cost, which is operational rather than usage guidance. Nothing tells the agent which scenario selects this tool over its aliases.

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