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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds modest behavioral value by disclosing what the result contains (Manglik house details and cancellation conditions), but says nothing about permissions, determinism of results, or response shape beyond annotations.

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 first sentence is front-loaded and dense with useful enumeration. The second — 'Trikaal Vaani, Swiss Ephemeris' — is a branding/vendor tag that gives an agent no actionable selection or invocation information and dilutes conciseness.

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?

With 7 parameters and no output schema, the description is adequate on inputs (schema covers them) but thin on what the agent gets back — only a hint about Manglik house details and cancellation conditions. For a specialized astrology computation with no output schema, more about the result structure would help.

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 100% across all 7 parameters, including units, ranges and the 12:00-default convention for unknown birth time, so the schema does the heavy lifting. The description contributes no additional parameter meaning, which is the baseline case.

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?

Names a specific verb (Checks) and resource (dosha) and enumerates the exact doshas covered — Kaal Sarp, Pitra, Guru Chandal, Grahan, Mangal/Manglik — plus the extras returned (house details, cancellation conditions). That is far more specific than siblings like yog_check or weak_planet, though it never explicitly positions itself against them and the trailing vendor string adds no clarity.

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?

Usage is only implied: an agent can infer this is called with birth data when dosha analysis is wanted, but there is no when-to-use/when-not-to-use statement and no pointer to alternatives such as janam_kundali (full chart) or yog_check (yogas). With 21 siblings, routing guidance is a real gap.

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