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

With annotations already declaring openWorldHint=false and destructiveHint=false, the description adds meaningful context: account requirements, private-account operation, authentication/audit/rate-limit behavior, and explicit exclusions for geocoding, web search, external recipients, and publishing. It does not explain the readOnlyHint=false annotation, which is somewhat surprising for a get-style operation, but it does not clearly contradict it.

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 is front-loaded in the first sentence, and the remaining sentences add prerequisites, privacy boundaries, and operational constraints. It is somewhat dense and repeats the private-account idea, but the length is defensible for a tool with account and data-boundary constraints.

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?

Because an output schema exists, the description need not explain return values in detail. It covers account prerequisites, privacy scope, data sources, and excluded behaviors well. The main remaining gap is the undocumented language parameter.

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?

There is one parameter, language, and the schema description coverage is 0%. The description does not mention language at all, so it provides no guidance on what the parameter controls, whether it affects response language, or what null/default means. It therefore fails to compensate for the low schema 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?

The description states a specific verb and resource: it returns the connected user's current Vimshottari period plus a sidereal transit snapshot, including transits to natal houses and current antardasha/pratyantardasha. That is much more specific than the name alone. However, it does not explicitly distinguish this tool from close siblings such as get_dasha_timeline or get_transits_to_chart.

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?

The description gives useful prerequisites and boundaries: a connected Vedara account with a completed birth profile, saved or explicitly supplied coordinates, and no public geocoding or external publishing. It does not say when an agent should choose this tool over siblings like get_dasha_timeline, get_transits_to_chart, or today_for_me, so usage is only implied.

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