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

Annotations already declare a safe, idempotent, non-destructive read, so the safety profile is covered. The description adds useful content context (what the sub-lord chain is for) and a credit cost, but says nothing about auth, rate limits, or response shape beyond the implied Mars sub-lord chain.

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?

Two tight sentences with the purpose front-loaded, followed by compact group/cost metadata. No filler, though the value proposition could be sharpened against siblings in the same space.

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 values need no explanation, and annotations cover safety. However, for a 15-parameter tool with low schema coverage, the definition leaves parameter selection and sibling routing unexplained, making it only minimally complete.

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?

With 15 parameters at only 33% schema description coverage, the description must carry weight but adds zero parameter guidance. Required birth-time and geo inputs (date, time, latitude, longitude) and ambiguous toggles like cosmogram and zodiacType are undocumented in both places.

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 names the specific resource (Manglik dosha) and its distinguishing feature (KP sub-lord precision, Mars sub-lord chain), which separates it from the Parashara and Lal Kitab manglik siblings at least by implication via the name. It stops short of explicitly contrasting with those sibling systems, so an agent must infer the school from the tool name rather than the prose.

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?

It hints at a use case (transit-trigger analysis) but gives no explicit when-to-use rule and never names the alternative manglik tools (lal_kitab_manglik, parashara_mangal, manglik_check). An agent has no guidance on selecting this over its near-duplicate siblings.

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