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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds two genuinely useful operational facts the annotations do not carry: it costs 10 credits (Tier 1) and belongs to the Hellenistic: Schmidt group. It says nothing, however, about what the computation returns or any input constraints.

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?

Very short and front-loaded: one-line purpose statement followed by group, cost and alias metadata. Nothing is padded, though the terseness borders on under-specification rather than efficiency.

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?

This is a specialized Hellenistic technique requiring full natal birth data plus a target age, sitting among hundreds of astrological siblings, and the description explains none of the technique, its inputs' purpose, or its output. An output schema exists so return values need not be described, but the agent has no basis for choosing this tool over the other Schmidt-tradition or time-lord tools.

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% — the nested body schema documents date/time/latitude/longitude, timezone, houseSystem, ayanamsa and the compact-mode fields in detail — so the schema does the heavy lifting and a baseline 3 is appropriate. The description adds no parameter meaning of its own; notably the required targetAge field carries no schema description either.

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' names the technique's domain but is essentially a restatement of the title 'Lord of Prediction' and never says what the tool actually computes or returns. It does locate the tool in the 'Hellenistic: Schmidt tradition' group, which helps place it among siblings, but an agent still cannot tell what a 'lord of prediction' result looks like.

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 at all — nothing says when to pick this predictive-time-lord technique over profections, zodiacal releasing, firdaria, or the dozens of other timing tools in the sibling list. The only routing information is that it is a 'Cursor-friendly alias' of astroway_hellenistic_schmidt_lord_of_prediction, which identifies a duplicate rather than a usage condition.

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