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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description usefully adds the group and the cost (10 credits, Tier 1), which is real behavioral context an agent may need for budgeting. It does not, however, disclose what inputs drive the analysis or what the result contains.

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 text is short and front-loaded, with no filler sentences. However, it is minimal by under-specification rather than by disciplined editing, and the bracketed metadata lines carry more weight than the actual purpose statement.

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-value explanation is not required. But for a 15-parameter analysis tool with only 33% schema coverage and no behavioral or usage detail, the description leaves the agent without enough to invoke it confidently or distinguish it from 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, so the description must compensate and it adds nothing at all. Required fields (date, time, latitude, longitude) and the several undocumented enum/boolean params (cosmogram, ayanamsaId, zodiacType, houseSystem) get no clarification. This is a clear gap given the low coverage.

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?

"Parental imagos analysis" essentially restates the title/name (Greene: Parental Imagos) without stating what the analysis actually computes or returns. It provides no verb+resource distinction from the sibling astroway_psyg_parental_imagos, which appears to be the same concept under a different prefix. An agent cannot tell what this produces versus its neighbors.

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, when-not-to-use, or alternative guidance anywhere in the description. The presence of a near-identical sibling (astroway_psyg_parental_imagos) makes routing guidance especially valuable, and none is given. The only orientation is the bracketed group and cost tags.

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