Pet Temperament

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

Annotations already declare readOnly, idempotent, non-destructive, so the safety burden is light. The description adds genuinely useful non-schema context: the POST endpoint, the four required inputs, and a 10-credit Tier 1 cost, which lets an agent reason about expense before calling. It still says nothing about what "short" means in practice (length of output, units, whether it is cached).

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 prose sentence is admirably front-loaded and free of padding, and the bracketed metadata lines are scannable. But the overall result is under-specified rather than economical: the short length comes from omission, not from compression of necessary content.

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 13-parameter tool with 23% schema coverage, the description leaves too much unexplained: sidereal vs tropical handling, house system choice, the ayanamsa aliasing, and the timezone/timezoneOffset interaction are all invisible. An output schema exists, so return values need not be described, but the invocation-side gap remains large.

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 23%, so the description must carry weight, but it merely restates the four required fields already encoded in the schema's required array. The nine optional parameters — zodiacType, houseSystem with its 25 enums, ayanamsa vs ayanamsaId, cosmogram, and timezone vs timezoneOffset — get no explanation here, and most have no schema descriptions either.

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?

"Short temperament-only summary" identifies the kind of output (a temperament summary, deliberately brief) but gives no verb, no indication that it is computed from a pet's birth data, and no differentiation from close siblings such as astroway_pet_personality or astroway_pet_sun_sign_meaning. An agent can guess the topic but not why it would pick this over the adjacent pet tools.

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 and no named alternative. The word "only" hints at a narrower scope than the personality tools, but that implication is never made explicit, and no prerequisites or exclusions are stated.

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