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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds genuinely useful context the annotations do not: cost (10 credits, Tier 1) and the POST endpoint. It says nothing about the shape of the calculation or output, but with annotations carrying safety this is adequate.

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 lines are scannable and front-loaded, and no sentence is padded. However, the whole payload is a stub rather than a tight summary, so it reads as under-specification rather than disciplined conciseness.

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 described, and annotations cover safety. But for a 15-parameter specialized Hellenistic technique with a nearly identical sibling, the description omits what the technique produces, how it differs from astroway_hels_derivative_houses_method, and any guidance on the optional chart-configuration parameters that heavily shape the result.

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 carries a compensation burden it does not meet. It lists the four required fields (date, time, latitude, longitude), which merely duplicates the schema's required array, and explains none of the optional inputs (fields, ayanamsa, zodiacType, houseSystem, precision, etc.).

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?

"Derived-house technique" restates the title/name without stating what the tool actually computes or returns. There is no verb or resource explanation, and no differentiation from the near-identical sibling astroway_hels_derivative_houses_method. The metadata brackets add endpoint/cost framing but not purpose.

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?

No when-to-use guidance, no prerequisites, and no named alternatives are given. In a catalog of hundreds of astrology tools, the agent has no signal for choosing this over the sibling derivative-houses methods. The only contextual hint is the implicit group label.

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