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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only a list of returned artifacts and discloses nothing behavioral beyond that, such as computational cost, dependency on chart inputs, or how the outputs differ from the narrower sibling tools. Given the annotation coverage this is adequate but thin.

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?

A single dense sentence with no filler, and the distinctive artifacts are front-loaded. It could be slightly better organized given the number of items, but nothing wasted.

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?

Although an output schema exists and relieves the description of explaining return values, this is a complex 9-parameter tool with an anyOf location requirement and multiple overlapping siblings, none of which the description addresses. It omits required-input guidance and completely forgoes the routing information an agent needs to choose it correctly.

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%, leaving date, time, topic, name, latitude, and longitude undocumented in the schema, and the description does not compensate. It only hints at topic filtering ('topic-specific'), with nothing about the required place-vs-coordinates anyOf structure or the meaning of the remaining inputs.

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 enumerates the outputs (Vimsopaka, Ishta/Kashta, cross-Varga synthesis, special Lagnas, Yoga candidates, Dasha status), which conveys roughly what the tool produces, but it is framed as a bag of return contents rather than a crisp verb+resource statement. It draws no boundary against overlapping siblings such as calculate_strength_profile, analyze_varga, analyze_yogas, or calculate_dasha_system, all of which appear to cover pieces of the same territory.

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. With heavily overlapping siblings like analyze_chart_topic and calculate_strength_profile, the absence of any routing signal leaves the agent to guess.

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