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

Annotations already establish readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The only added trait is the cost tag (10 credits, Tier 1), which is genuinely useful, but nothing is said about what the computation requires, whether the four required birth-data inputs are mandatory, or how heavy the operation is.

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?

Two short lines plus bracketed metadata tags — nothing is padded or repeated, and the purpose statement leads. However, the brevity reflects under-specification rather than disciplined conciseness.

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 15-parameter, 10-credit psychological report tool, the definition is far too thin. An output schema exists, so return values need not be described, but the description never conveys what the Saturn-shadow analysis contains or what makes the required birth data meaningful.

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 is expected to compensate — and it contributes nothing about any parameter. The schema does richly document a few key fields (fields, ayanamsa, timezone, precision, timezoneOffset), which keeps this above the floor, but city, cosmogram, zodiacType, and the four coordinate/date inputs remain unexplained.

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?

"Saturn-as-shadow integration work" largely restates the tool's own title ("Greene: Saturn Shadow") without a concrete verb or resource. It gives no indication of what is actually produced (a report? a chart? an interpretation?) and offers nothing to distinguish it from the near-identical sibling astroway_psyg_saturn_shadow.

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 guidance, no prerequisites, and no routing to alternatives. With a sibling named astroway_psyg_saturn_shadow sitting directly in the same family, the omission is especially costly — an agent has no basis to choose between them.

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