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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety behavior is covered. The description adds the credit cost and tier, which is genuinely useful planning context, but discloses nothing about the operation itself (e.g., that a full birth/event moment is required).

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 text is short and front-loads the resource, with metadata cleanly bracketed at the end. But the brevity is under-specification rather than economy: the one substantive sentence carries almost no operational information.

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 not be explained. Still, a 15-parameter, 4-required charting tool in a dense cosmobiology family needs more than a body count; there is no indication of what distinguishes this result from the other Hamburg School endpoints an agent could call.

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?

With 15 parameters and only 33% schema description coverage, the description bears responsibility for compensating, and it says nothing about any parameter. It does not clarify required date/time/lat/long inputs, the timezone-vs-timezoneOffset precedence, or which knobs affect TNP output versus general chart output.

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 the resource — the 8 Hamburg trans-Neptunian bodies — which does spell out the 'TNP' acronym in the title and give a count. However, it never states the action (compute a chart's positions? list the bodies?) and gives no basis for choosing it over sibling cosmobiology tools like witte_formulas, dial_90, or midpoint_pictures.

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, when-not-to-use, or alternative tool guidance. The [Group] and [Cost] tags provide context about billing and family, but nothing tells an agent which input conditions or astrological question should route here rather than to another Hamburg School tool.

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