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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds genuinely new operational context the annotations do not carry: the credit cost and tier (10 credits, Tier 1) and the exact required input set, which is comparable to disclosing rate/cost 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?

Front-loaded with the purpose, then terse bracketed metadata with no filler sentences. The endpoint URL is the only arguably redundant element, and the whole definition is short enough to scan instantly.

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 no explanation, and required inputs plus cost are stated. However, for a 15-parameter tool at 33% schema coverage sitting in a dense cluster of near-identical Hellenistic lot tools, the definition does not explain the optional parameters or justify choosing it over its siblings, leaving real gaps.

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 only 33% across 15 parameters, so the description carries the burden of compensating — and it does not. It repeats the four required fields already listed in the schema's 'required' array and says nothing about the meaningful optional inputs (fields compact mode, ayanamsa/sidereal school, timezone vs timezoneOffset, zodiacType, houseSystem, precision).

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 names a specific resource ('All 15 Hermetic Lots per Brennan §11') and scopes it to a named author/tradition, which separates it from the Greenbaum, Hand and Schmidt lot tools in the sibling list. It never states an explicit verb (compute/derive), and the differentiation from other lot endpoints is carried by the '[Group: Hellenistic: Brennan tradition]' tag rather than prose.

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?

Usage is only implied: the agent must infer that this is the tool for the 15-lot Brennan set specifically. There is no statement of when to prefer this over astroway_hellenistic_hand_lots_of_seven or the Greenbaum lot endpoints, and no prerequisites beyond the required-field list.

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