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

Annotations already declare this a read-only, idempotent, closed-world, non-destructive call, so safety is covered. The description adds genuine behavioral context the annotations do not: cost (10 credits, Tier 1) and the underlying endpoint. It does not describe the return shape, though an output schema exists.

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 description is short and front-loads the purpose before a compact bracketed metadata block (group, endpoint, cost, alias). Every line carries distinct information with no filler, though the bracketed format is more machine-metadata than prose guidance.

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?

With full annotations, full schema coverage, and an output schema, most structured burden is already carried elsewhere. What remains missing is conceptual completeness: an agent still cannot tell what a 'Lord of Prediction' returns or how targetAge is applied, leaving the tool's core semantics under-explained despite the procedural metadata.

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%, so the nested body, fields, and precision parameters are already documented in structured data; the accepted response-'fields books baseline 3. The description adds no parameter meaning of its own (notably it says nothing about the required targetAge), so it neither helps nor compensates.

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 phrase "Predictive significator selection" nominally pairs a resource (predictive significator) with an action (selection), but it is jargon-heavy and largely restates the title 'Lord of Prediction' without explaining what the technique produces. The most useful clarifying line is the alias note, which at least tells the agent this duplicates `astroway_hellenistic_schmidt_lord_of_prediction`, but nothing distinguishes it functionally from the other Schmidt-tradition siblings.

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 guidance on when to use this tool versus alternatives such as the canonical `astroway_hellenistic_schmidt_lord_of_prediction` or neighboring Schmidt techniques. The alias remark implies equivalence rather than a selection rule, and nothing states prerequisites (e.g., that targetAge drives predictive timing).

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