Communication Style

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

Annotations already declare this a safe, idempotent, non-destructive, closed-world read, so the description does not need to cover safety. It does add genuinely useful context the annotations lack: the POST endpoint shape, the four required inputs, and the 10-credit Tier 1 cost. It says nothing about what the computation does with the birth data or what assumptions (default ayanamsa, house system) apply.

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 purpose sentence is front-loaded and the bracketed metadata lines each carry information (group, endpoint, required inputs, cost). Nothing is padded, but the definition is undersized for a 13-parameter chart request, leaving the structure tidy yet thin.

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. However, for a tool requiring the subject's date, time, latitude, and longitude, the description never says whose birth data is needed (the pet's), whether the values are mandatory or best-effort, or how timezone defaults are resolved. For a 13-parameter request the definition is not complete enough to call confidently.

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?

Thirteen parameters with only 23% schema description coverage, and the description only echoes the four required fields already stated in the schema's required array. It adds no meaning for the optional but consequential inputs (ayanamsa, zodiacType, houseSystem, timezone vs timezoneOffset) that dominate this tool's complexity. With low coverage the description was expected to compensate and does not.

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 says 'How best to communicate with this pet', which identifies the resource (pet communication guidance) but only restates the name/title in different words. It gives no way to tell it apart from the many adjacent pet sibling tools such as astroway_pet_training_style, astroway_pet_temperament, or astroway_pet_play_style. An agent can guess the topic but not the precise deliverable.

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 statement, no prerequisite, and no named alternative. The bracketed lines list endpoint, required fields, and cost, which is operational metadata rather than selection guidance, so an agent must infer from the tool name alone whether to pick this over pet_training_style or pet_personality.

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