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 without the description. The description adds the endpoint (POST /v1/draconic) and a billing cost, which are genuinely beyond the annotations, but nothing about how optional flags like zodiacType or ayanamsa alter the draconic computation.

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?

One definitional sentence followed by compact bracketed metadata; front-loaded and free of filler. Slightly dense but every line carries information, and the bracketed block is 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 no explanation, but this is a 15-parameter tool where interactions matter — e.g. whether draconic shifting is applied before or after zodiacType/ayanamsa/houseSystem settings. The description supplies the core formula and cost but leaves those interaction questions unaddressed.

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, and the description contributes nothing beyond restating the four required fields already listed in the schema's "required" array. The eleven optional parameters (zodiacType, houseSystem, ayanamsa, fields, precision, cosmogram, etc.) are left entirely to the schema, so the description fails to compensate for the coverage gap.

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?

Names a specific verb and resource ("Calculate the draconic chart") and even defines the technique (shifting longitudes so 0° = True Node), which makes it clearly separable from specialized_harmonics, heliocentric, and horizon. It stops short of naming a sibling alternative, so it is clear but not explicitly differentiated.

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 statement of when to pick draconic over harmonics, heliocentric, or vedic_divisional, and no prerequisites or exclusions. The only decision-relevant information is the cost line (20 credits, Tier 2) and the required-parameter list, which is metadata rather than usage guidance.

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