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

Annotations already declare readOnlyHint=true, openWorldHint=false, idempotentHint=true, and destructiveHint=false, so the safety and idempotency profile is fully covered. The description adds only the cost (10 credits, Tier 1) and group, which is useful but doesn't disclose return format, computation basis, or limits beyond what structured fields provide. With annotations carrying the main behavioral load, a 3 is appropriate.

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 description is a single terse fragment plus two bracketed metadata lines. It is short, which is good, but it is under-specified rather than concise; it lacks the front-loaded clarity an agent needs to select the tool.

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 15-parameter (many undocumented) tool with an output schema and rich annotations, the description is far too sparse. It doesn't explain the element-based logic, what 'recommended/avoid activities' contains, or how intensity is derived, leaving the agent without enough context to use it confidently.

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 there are 15 parameters. The description mentions nothing about any parameter, leaving many (city, name, date, time, latitude, longitude, zodiacType, houseSystem, etc.) undocumented in both schema and text. It fails to compensate for the low coverage, so it scores below the baseline of 3.

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 resource (exercise activities and intensity) tied to elements, which is a specific concept, but it doesn't clearly distinguish this from siblings like astroway_wellness_yoga, astroway_wellness_diet, or astroway_pet_exercise_needs. It's a vague fragment rather than a clear verb+resource statement, leaving the agent to infer the tool's exact purpose from the name alone.

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 guidance about when to use this tool versus alternatives like astroway_wellness_yoga or astroway_wellness_diet, nor any mention of prerequisites or exclusions. The agent gets no routing help among the many wellness siblings.

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