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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds two genuine behavioral traits beyond that: output is 'evidence-linked' and it avoids deterministic predictions. However, it says nothing about required auth, birth-data prerequisites, or how evidence is surfaced.

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?

It is a single short sentence with no filler, so it is not bloated, but its brevity comes at the cost of substance. The one clause that matters is front-loaded after the redundant restated name.

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 10-parameter, dual-input-mode analysis tool, this is substantially incomplete: it omits the place/coordinates requirement, the topics enum meaning, and the significance of asOfIso. An output schema exists, so return values need not be explained, but the input and routing context is missing.

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 30% (10 params; place, timezone and timezoneOffset described). The description adds zero parameter meaning and does not compensate for undocumented date, time, name, topics, or asOfIso, nor does it explain the anyOf place-vs-coordinates input rule.

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 largely restates the tool name ('analyze nakshatra profile') with two qualifiers, rather than stating a specific verb+resource outcome. It never says what a nakshatra profile actually is or how it differs from closely-related siblings like calculate_devata_profile, get_natal_panchanga, or analyze_chart_topic.

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, or alternative-tool guidance. The only hint is the phrase 'without deterministic outcome claims,' which describes a stance on results rather than a condition for selecting this tool over its many analyze_* siblings.

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