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

Annotations already declare the safety profile (readOnlyHint, idempotentHint, non-destructive), so the bar is lower. The description adds useful context by naming the returned content and disclosing a 'disclaimer' and a 10-credit Tier 1 cost, but says nothing about computation behavior, precision defaults, or what the sidereal/house-system options actually change.

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 compact lines with the core content front-loaded and no filler; the metadata tags are boilerplate but harmless. It is efficient, though its brevity is partly under-specification rather than pure economy.

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 not be explained, but for a 15-parameter astrological calculation tool with 33% param coverage and no usage guidance, the description is too thin. It omits what the numerous chart-configuration parameters do and when to reach for this tool over its 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 only 33% across 15 parameters, and the description adds no parameter meaning at all. Several inputs (city, date, name, latitude, longitude, cosmogram, zodiacType, houseSystem) are undocumented in both schema and description, so the description 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?

States a specific verb and resource ('Full natal chart for the pet') and enumerates its contents (sun, moon, ASC + planets), which is more concrete than a bare restatement of the title. It does not, however, explicitly distinguish itself from the many other pet-astrology siblings (pet_personality, pet_sun_sign_meaning), leaving the agent to infer that this is the comprehensive chart.

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 alternatives, no prerequisites, and no exclusions. The only framing is a group tag and cost, which does not tell an agent which of the ~13 pet-astrology siblings to pick.

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