Pet Personality Profile

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description contributes genuinely new behavioral information in the cost line (10 credits, Tier 1), which matters for an agent budgeting calls. It says nothing about latency, caching, or what the breakdown returns, but the output schema covers returns.

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?

Very short and front-loaded, with the one descriptive sentence first and structured metadata after. The bracketed metadata is useful rather than padding, though the description line itself is thin relative to the tool's complexity.

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 astrological calculation tool with only 23% schema coverage, the description omits everything about the optional configuration parameters and the scope of the "full breakdown." The output schema relieves it of documenting return values, and cost is disclosed, but an agent still cannot tell how this report differs from the twelve other pet tools.

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% across 13 parameters, so the description carries a heavy burden and does not meet it. It lists only the four required fields, which are already declared in the schema's required array, and never explains ayanamsa vs. ayanamsaId, zodiacType, houseSystem, cosmogram, or timezone/timezoneOffset interplay.

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?

"Full personality breakdown" essentially restates the tool name (pet_personality) and the title (Pet Personality Profile) without stating what the output contains or how it differs from the many sibling pet tools (pet_temperament, pet_sun_sign_meaning, pet_communication_style, pet_birth_chart). The endpoint line confirms a POST to /v1/pet/personality but adds no semantic distinction.

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, no prerequisites, and no mention of any alternative sibling tool. The bracketed [Required: date, time, latitude, longitude] restates schema-required fields rather than helping the agent choose between this and pet_temperament or pet_birth_chart.

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