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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context the annotations lack: the endpoint (POST /v1/pet/personality) and the credit cost/tier, which matters for an agent deciding whether to spend a call. It says nothing about what the breakdown contains or whether the call is expensive in latency.

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?

It is short and front-loads the one-sentence purpose, then switches to bracketed metadata lines that are easy to scan. However, the leading sentence is so thin that the brevity reflects under-specification rather than efficiency.

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 calculation with an output schema present, the return values need no explanation, but the description is still far too thin: it never says what the 'personality breakdown' comprises, how it differs from other pet tools, or how the many optional chart settings affect the result.

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?

With 15 parameters and only ~33% schema description coverage, the description needs to compensate, but it only re-lists the four required fields (date, time, latitude, longitude) that the schema already enforces. It adds nothing about timezone vs timezoneOffset interaction, ayanamsa, house system, or the compact-mode fields parameter.

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 'Full personality breakdown' merely restates the title 'Pet Personality Profile' without naming a verb, a resource, or the pet subject. It does not distinguish this tool from close siblings like astroway_pet_temperament, astroway_pet_sun_sign_meaning, or astroway_pet_birth_chart, so an agent cannot tell which of them to pick.

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 statement of when to use this tool versus its pet-domain siblings, and no prerequisites beyond the bare list of required inputs. The only usable routing signal is the cost line (10 credits, Tier 1), which is operational rather than guidance about selection.

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