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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered by structured data. The description contributes non-annotation operational context in the form of the credit cost ('10 credits, Tier 1'), but says nothing about the targetAge semantics, computation behaviour, or what 'full classical condition' entails.

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?

A single front-loaded sentence plus two bracketed metadata tags — no filler, nothing repeated from the schema. It is efficient, though arguably at the cost of the guidance an agent needs.

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 described, and the input schema is exhaustively documented, which lowers the bar. What remains missing is the routing context (which profection tool to use when) and any note on what targetAge drives, which for a niche Hellenistic technique would meaningfully help an agent call it correctly.

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 100% with a very detailed body schema (formats, rejected short forms, timezone handling, house-system letters), so the schema carries the burden. The description adds no parameter meaning of its own; baseline 3 applies.

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 one-line description names a specific technique and output ('Annual profection year-lord with full classical condition'), which is clearer than a bare tautology. It does not, however, distinguish itself from near-identical siblings such as astroway_helb_profections_detail, astroway_prognostics_profections or astroway_hellenistic_hand_perfections, so an agent cannot tell which profection variant to pick from the description alone.

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, when-not-to-use, or alternative-tool guidance. The [Group: Hellenistic: Brennan tradition] tag is a taxonomy label, not a routing instruction, and it is the only thing helping the agent choose among the several sibling profection tools.

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