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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only a group tag and a cost tier (10 credits), which is mildly useful, but says nothing about what the computed output contains or any limits of the technique.

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?

It is short, but the brevity is under-specification rather than conciseness: the formula fragment is not self-explanatory and no sentence earns its place by conveying actionable 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?

For a 16-parameter, complex cosmobiology computation with an output schema, the description is wholly inadequate. An agent cannot determine inputs, defaults, or the nature of the result from it.

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 16 parameters and only 31% schema description coverage, the description is expected to compensate for the documentation gap, and it contributes nothing — no mention of date/time/latitude/longitude requirements, ayanamsa vs ayanamsaId, timezone handling, compact-mode fields, or cosmogram/TNP flags.

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 reduces to the tool's title plus a formula fragment ('Witte planetary pictures A+B−C=D') with no verb stating what the tool actually produces (e.g., computes/returns planetary picture contacts for a chart). It is close to a restatement of the name rather than a statement of function, and it does nothing to separate it from siblings like midpoint_pictures or personal_point_tree.

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 guidance on when to use this tool, no prerequisites, and no mention of the many close alternatives in the Cosmobiology group. An agent has no basis to choose this over astroway_cosmobiology_midpoint_pictures or personal_point_tree.

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