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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds two facts not present in structured data – the 10-credit Tier 1 cost and the tradition grouping – plus the depth hint 'full classical condition'. It says nothing about targeting a specific profection year or how the result is shaped, so with annotations carrying the safety burden a 3 is fair.

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 substantive line is front-loaded and short, with metadata tags on separate lines that do not interrupt reading. The cost and alias notes are compact and earn their place as routing aids. No filler prose.

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 an output schema present, the description is not obliged to explain return values, and it identifies the calculation performed. However, it never connects targetAge to the profection year being computed – the key input for this tool – and gives no hint about the scope of 'full classical condition' output. Adequate but with a clear gap for an agent to invoke it confidently.

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 birth-data block, fields and precision params are already documented in the schema, including the timezone/offset and houseSystem caveats. The description adds no parameter-level meaning of its own, which is the expected baseline 3 when the schema does the heavy lifting. Notably targetAge, the one field that distinguishes this from a generic natal chart, is left to the schema.

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?

Names a specific resource – the annual profection year-lord with its full classical condition – which is a concrete astrological deliverable rather than a restatement of the title. It also discloses that it is an alias of astroway_hellenistic_brennan_profections_detail, helping the agent recognize the duplicate. It stops short of distinguishing this from sibling profection tools such as astroway_prognostics_profections, so differentiation is only partial.

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 statement of when to call this versus the canonical astroway_hellenistic_brennan_profections_detail or the other profection/prefection tools. The group tag '[Hellenistic: Brennan tradition]' hints at the school but gives no selection criteria. The alias note implies interchangeability but never says to prefer one over the other.

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