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 by structured data. The description's only added behavioral context is the cost tier (10 credits, Tier 1) and the tradition grouping, which the annotations do not carry. It says nothing about output shape, precision, or how the Lots are derived.

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-loaded with the resource statement, and the bracketed group/cost metadata is useful. However, the brevity reflects under-specification rather than tightness, so it cannot score above a middling value.

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 tool with 15 parameters and multiple required astronomical inputs, the description is far too thin. An output schema exists so return values need not be explained, but the agent still lacks any statement of what makes this tool different from the numerous other Hellenistic Lot tools in the sibling list.

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% and the description contributes zero parameter meaning. Undocumented parameters include city, name, latitude/longitude, cosmogram, zodiacType, houseSystem and ayanamsaId, and the description does nothing to compensate for that gap even though required inputs like date, time and coordinates drive the whole computation.

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 mostly restates the tool name: the name says 'lots_of_seven' and the text says 'Seven primary Lots per Hand.' It does not define what a 'Lot' is, list the seven Lots, or explain what 'per Hand' means to an agent. It gives no verb (compute/derive) and barely distinguishes itself from the sibling astroway_hellenistic_brennan_lots_15.

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 routing to alternatives such as astroway_hellenistic_brennan_lots_15 or the individual Lot tools (astroway_helg_daimon_tyche_axis, astroway_hellenistic_greenbaum_lot_of_eros_detail). The agent must infer usage entirely from the name.

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