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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds genuinely useful operational context the annotations don't carry: the POST endpoint and the 10-credit (Tier 1) cost. However it says nothing about what the temple-house doctrine output contains or any constraint on its interpretation.

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?

One short sentence plus compact bracket metadata; the core purpose is front-loaded and there is no filler prose. The metadata lines are dense and scannable, though the block conveys more about billing than about usage.

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 formatting needn't be explained, but the semantic gaps remain: an agent knows the required inputs and the cost yet has no idea what a 'temple doctrine' result represents or when to invoke it. For a 15-parameter chart endpoint with 33% schema coverage, the description is not sufficient.

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 must compensate, and it does not. It merely repeats the four required fields already enforced by the schema and omits any mention of the substantive optional inputs (ayanamsa/ayanamsaId, zodiacType, houseSystem, timezone vs timezoneOffset, fields/precision).

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?

"Temple-house assignments per Greenbaum" names a specific calculation and its tradition, which is better than a tautology, but it uses domain jargon ("temple-house assignments") that an agent cannot translate into what the tool actually computes or returns. It also does not distinguish itself from the near-identical sibling astroway_helg_temple_doctrine.

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 no when-to-use guidance, no prerequisites, and names no alternative tool (e.g. why pick this over astroway_helg_temple_doctrine or the other Greenbaum endpoints). The [Required:] line restates the schema's required array but does not tell the agent when this tool is the right choice.

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