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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description usefully adds the endpoint, the credit cost (10 credits, Tier 1), and the required inputs, which is real behavioral context beyond the annotations, but it omits any auth or rate-limit notes.

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?

Purpose is front-loaded in one sentence, followed by a compact metadata block. The required-parameters line duplicates the schema, but the whole definition is short and easy to scan.

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, and the description notes what the output contains. However, for a 15-parameter tool with low schema coverage and no usage guidance, the definition leaves the agent under-informed about how to invoke it well.

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. It only restates the four required parameters already present in the schema's required array and explains none of the optional controls (timezone, ayanamsa, houseSystem, fields, precision).

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?

States a specific subject and result: body parts ruled by sun-sign via traditional Melothesia, returning primary/secondary/vulnerabilities. This is clearly distinct from wellness siblings like herbs, diet, or exercise, though it never names an alternative to sharpen the boundary.

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 or when-not-to-use guidance, and no mention of the wellness siblings it could be confused with. An agent can infer it is a medical-astrology reading, but nothing routes it against alternatives.

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