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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered structurally. The description usefully adds behavioral context the annotations lack: it is a POST at /v1/wellness/exercise costing 10 credits (Tier 1). It does not disclose response shape or any failure behavior, so a 3 is fair.

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 content line plus a tight bracketed metadata block; front-loaded and free of filler. The metadata lines earn their place by conveying cost and endpoint, though the required-params line duplicates the schema.

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?

With an output schema present, return values need not be explained, and annotations cover the read-only safety profile, so the description is adequate for a basic call. However, for a 15-parameter tool with low schema coverage, it omits any guidance on the many astrological parameters an agent may need to set.

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 heavier burden — yet it merely restates the four required fields already marked required in the schema (date, time, latitude, longitude). The optional ayanamsa, timezone, houseSystem, fields and precision parameters get no semantic help from the description.

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 states the output content specifically — 'element-based intensity + recommended/avoid activities' — which tells an agent what this tool returns and distinguishes it from pure chart tools. It does not differentiate from close wellness siblings like astroway_wellness_yoga or astroway_wellness_diet, so it stops short of a 5.

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 wellness siblings. The metadata block supplies endpoint, required params and cost, but none of that tells the agent when this tool is the right choice versus yoga, diet, or cycle.

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