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 structurally. The description adds only cost/group metadata (10 credits, Tier 1) and nothing about what the computation requires or how results should be read. With annotations carrying the safety burden, this is a thin contribution.

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 two lines are tightly worded and the group/cost metadata is genuinely useful front-loaded context, so there is no padding. However, 'appropriately sized' fails badly for a 15-parameter tool in an obscure domain — the brevity reflects under-specification rather than discipline.

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 not be explained, and annotations cover safety. But given a 15-parameter, four-required tool in a specialized Hellenistic technique, the description leaves the purpose opaque and the inputs unexplained, so an agent cannot confidently select or invoke it.

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?

The schema has 15 parameters at only 33% description coverage, and the four required ones (date, time, latitude, longitude) carry no schema descriptions at all. The description supplies zero parameter meaning, adding nothing about formats, defaults, or which options matter for a temple-doctrine computation. With low coverage, the description was required to compensate and does not.

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 is a noun fragment that restates the title 'Temple Doctrine' as 'Temple-house assignments per Greenbaum' with no verb and no indication of what the tool actually computes or returns. It does not distinguish this tool from the near-identical sibling astroway_helg_temple_doctrine, nor from the other Greenbaum-tradition tools. This is closer to a tautological restatement of the name than a stated purpose.

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 guidance, no prerequisites, and no mention of alternatives such as astroway_helg_temple_doctrine or the other Hellenistic Greenbaum tools. The [Group: ...] tag hints at a family but never says when this member 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.