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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful non-schema context: the credit cost (10, Tier 1) and the endpoint. It does not explain what 'short' means for depth or output size, nor whether the result is deterministic across calls, so it adds some but not rich behavioral context.

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 main line is a single fragment with zero waste, and the bracketed tags are consistently structured and front-loaded. However, the brevity is closer to under-specification than disciplined concision, and the tag block carries more informational weight than the actual description sentence.

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, and the required-parameter set plus cost are stated. For a 15-parameter chart-derived tool, though, the description is thin: it never says what the temperament summary contains or why sidereal/house-system options matter here, leaving the agent to rely entirely on schema descriptions that cover only a third of the parameters.

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 3 of them are enums whose meanings rest entirely on bare enum lists (zodiacType, houseSystem codes). The description's '[Required: date, time, latitude, longitude]' merely restates the schema's required array and clarifies nothing about the 11 optional parameters, 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 states a clear resource and scope ('Short temperament-only summary'), and the endpoint tag (POST /v1/pet/temperament) confirms what is produced. The word 'only' plus 'short' gives some purchase against the sibling astroway_pet_personality, but there is no verb and no explicit statement of how it differs from the other pet readings.

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?

Nothing tells the agent when to choose this over astroway_pet_personality, astroway_pet_sun_sign_meaning, or the other ~13 pet_* siblings. It also does not say when this narrow summary is preferable to a fuller reading. The only inferred usage comes from the title and the word 'only'.

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