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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context beyond annotations — the POST endpoint, the 10-credit Tier 1 cost, and the group — but says nothing about response shape, determinism, or rate behavior.

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 single substantive sentence is front-loaded, and the bracketed tags (group, endpoint, required, cost) are compact and scannable. Nothing is padded, though the 'Required' tag is redundant with the schema and could be dropped.

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 annotations cover safety. However, for a 15-parameter tool with three enums, the description leaves too much unspecified — notably what 'element-based' derivation implies and how the pet's chart inputs map to the output — making it merely adequate.

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%, so the description carries a real burden, yet it only restates the four required parameters already declared in the schema's required array. Undocumented parameters (zodiacType, cosmogram, ayanamsaId, houseSystem, latitude/longitude semantics) get no clarification here, so it 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?

The description names the resource and output concretely: 'Element-based daily exercise minutes + recommended activities,' which tells an agent exactly what the call produces for a pet. It does not, however, differentiate itself from overlapping pet siblings like astroway_pet_play_style, astroway_pet_diet_by_sign, or the human-facing astroway_wellness_exercise, so an agent cannot tell which to pick from purpose 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 when/when-not guidance and no alternatives named. The agent is never told under what circumstances exercise-minutes advice is appropriate versus the neighboring play-style, temperament, or wellness-exercise tools, leaving selection to inference.

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