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

Annotations cover the safety profile (readOnly, idempotent, not open-world), and the description adds substantial behavioral context beyond them: deterministic JPL DE440 computation with no LLM, historical DST/LMT handling, ambiguity flagging instead of guessing, a meta.result_sha256 on every result, and $0.01/call pricing with 3 free calls plus the REST endpoint. It does not cover rate limits or failure modes in detail, so 4 rather than 5.

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 value is front-loaded in a single dense first sentence, and subsequent sentences cover method, ambiguity handling, outputs and pricing. The output list is effectively stated twice (first sentence and the 'returns Julian Days...' sentence), which is minor wasted space in an otherwise efficient description.

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 no output schema, the description fully carries the return-value burden by enumerating Julian Days (UT/TT), Delta T, LMT, true solar time and the equation of time. Combined with the all-optional 8-parameter schema and its own fallback rules, an agent has everything needed to call this 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%, so the schema already documents every parameter including the timezone-from-coordinates fallback and the ambiguous_time default. The description largely restates these behaviors (timezone resolved from coordinates, historical offset applied) without adding new syntax or format guidance, so the 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 opening line states a specific transformation (local birth time + place -> exact UT, UTC offset, Delta T, LMT, true solar time), which is a precise verb+resource statement no sibling tool covers. It also carves out its niche versus the chart-producing siblings by calling itself 'the step LLMs most often get wrong.'

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?

It clearly frames the context (use it to correctly convert a local birth time before other work) and notes behaviors that affect invocation, such as flagging ambiguous/non-existent times rather than guessing. It never names an alternative or an explicit when-not, so it stops short of a 5.

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