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

Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description does add genuinely useful non-schema context that annotations omit: a credit cost of 10 (Tier 1) and the Pet Astrology grouping. It says nothing about return shape or limits, but with an output schema present and annotations covering safety, a 3 is fair.

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?

Two short lines, front-loaded with the core statement, with no filler. The metadata lines are compact and arguably useful. It is efficient, though its brevity shades into under-specification rather than pure conciseness.

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 tool in a dense family of near-identical pet-analysis siblings, the description omits what makes it distinct, what the breakdown contains, and what the required birth data represents. The output schema relieves it of describing return values, and annotations cover safety, but the differentiation and input-orientation gaps are significant for this complexity level.

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, so the description is expected to compensate for the undocumented ones (city, name, date, time, latitude, longitude, cosmogram, zodiacType, houseSystem, ayanamsaId). It supplies zero parameter information – not even that a pet's birth date, time, and coordinates are required. The schema does document fields/ayanamsa/timezone/precision/timezoneOffset well, but the description leaves the coverage gap entirely unaddressed.

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 phrase "Full personality breakdown" names a resource (pet personality) and implies a verb (produce an analysis), so the general purpose is discernible. However, it never distinguishes itself from close siblings like astroway_pet_temperament, astroway_pet_sun_sign_meaning, or astroway_pet_communication_style, which all read as personality-adjacent. The word "Full" hints at breadth but no concrete scope is given.

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 contains no when-to-use guidance, no prerequisites, and no routing to alternatives, despite thirteen sibling pet tools that could plausibly be chosen instead. The only bracketed metadata is group and cost, which is not usage guidance. An agent must guess based on the name alone.

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