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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the safety bar is lower. The description still adds useful traits beyond the annotations: results are ranked, neutral-framed, carry citation state, use explicitly uncalibrated confidence, and are bounded by mandatory safety limits. These are meaningful interpretation caveats an agent would not otherwise know.

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 dense sentence that front-loads the core action and the output characteristics, with no filler or repetition. It is long but every clause carries content, though the compressed phrasing for a 12-parameter tool makes it read as packed rather than crisp.

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 high-complexity tool with an output schema present, the description need not explain return values, and it does summarize them adequately. However, it omits the location-input duality (place vs lat/long/timezone) and any usage routing, leaving real gaps for a 12-parameter astrological tool. Minimum viable but noticeably incomplete.

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 25% across 12 parameters, so the description is expected to compensate and largely does not. It only implies date-range scoping (startDate/endDate); it says nothing about the place-vs-coordinates anyOf, the required IANA timezone, language, timezoneOffset, or birthTimeAccuracyMinutes. Only one semantic hint is added over the schema.

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 gives a specific verb and resource (detects structural afflictions and Yogas, weights their Dasha activation, returns ranked themes), which is materially more precise than the title alone. It is distinguishable from nearby siblings like analyze_yogas or calculate_doshas because it names the Vimshottari weighting and ranked-output step. It stops short of explicitly saying how it differs from those siblings, so it is not a 5.

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 or when-not-to-use guidance, and no alternative is named despite many plausible siblings (analyze_yogas, calculate_doshas, analyze_transit_activation, fuse_timing). The date-range phrase implies a time-windowed use case but never states when an agent should pick this tool over the alternatives.

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