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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the cost tier (20 credits), the endpoint, and the return structure, but says nothing about auth requirements, rate limits, or how the components relate to each other. Adequate but limited added context.

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 main sentence is dense with domain jargon but front-loads the essential meaning, and the bracketed meta block (group, endpoint, required, cost) is cleanly structured. Slightly heavy on untranslated Sanskrit term names, but nothing is wasted.

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 the description need not detail return values, and it helpfully sketches them anyway. However, for a 15-parameter tool with low schema coverage and no usage guidance, the absence of any parameter or configuration guidance leaves a real gap.

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 33% across 15 parameters, so the description carries the burden of compensating and does not. It merely restates the four required parameters (date, time, latitude, longitude) that the schema already marks required, and never explains the semantics of ayanamsa, houseSystem, zodiacType, or the compact-mode fields/precision options.

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 a specific computed resource (strength of the twelve houses) and enumerates its three constituents: Bhavadhipati Bala, Bhava Digbala, and Bhava Drishti Bala. It clearly separates itself from the sibling shadbala tools, which compute planetary rather than house strength, and states the classical source (BPHS Adhyaya 27).

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 by the content: an agent can infer this is for house-strength analysis rather than planetary (shadbala_*) or transit (ashtakavarga) strength. There is no explicit when-to-use statement, no prerequisites, and no naming of an alternative tool to prefer in adjacent cases, despite a very large sibling set.

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