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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed world, so the safety profile is covered. The description adds genuinely useful non-annotation context: the cost (10 credits, Tier 1), the group, and the endpoint. It does not, however, explain what is computed or any constraints on interpretation, and the output schema carries the return shape.

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 one-line purpose is front-loaded and the bracketed metadata block is compact and scannable. Nothing is padded, though the boilerplate tags are structural scaffolding rather than substantive description.

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 chart-derived tool, the description is thin: it never states that output is computed from a natal chart at the given date/time/location, nor hints at the sidereal/house-system choices that materially change the result. Cost is disclosed and an output schema exists, but the agent is left without enough to call this confidently over its pet_* siblings.

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 33% across 15 parameters, so the description must compensate — and it does not. It merely repeats the four required names (date, time, latitude, longitude), which the schema already enforces, while the eleven optional parameters (zodiacType, houseSystem, ayanamsa, precision, fields, etc.) go unexplained. Listing required fields is zero-value duplication rather than added semantics.

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?

"How best to communicate with this pet" gestures at the output but names no verb or method — it doesn't say the result is derived from birth data. It also fails to differentiate from close siblings like astroway_pet_temperament, astroway_pet_personality, or astroway_pet_training_style, which an agent could easily confuse with it. Vague but not tautological.

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?

The description gives no when-to-use guidance, no prerequisites, and no pointer to alternatives among the many pet_* siblings. The bracketed [Required] line lists inputs but says nothing about when this tool is the right choice versus temperament, personality, or play_style.

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