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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's one genuine addition is billing context: "Cost: 10 credits (Tier 1)", which tells the agent this call has a real cost — useful, though nothing is said about computation behavior or failure modes.

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 description is short and the metadata tags are cleanly structured and front-loaded, so there is no wasted prose. However, its brevity comes from under-specification rather than economy — the single content sentence carries almost no 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-value details need not be explained, and annotations cover safety. But for a 16-parameter tool in a dense sibling cluster, the description leaves the agent unable to judge what result to expect or why to choose this tool over its cosmobiology neighbours.

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 31% across 16 parameters (city, name, withTnp, cosmogram, zodiacType, houseSystem and others undocumented), and the description mentions no parameter at all. With low coverage the description is expected to compensate, and it contributes zero parameter meaning.

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 phrase "Ebertin's personal points midpoint hits" names a technique but never states in plain terms what the tool computes or returns. It neither distinguishes itself from sibling cosmobiology tools such as midpoint_pictures or personal_point_tree, nor supplies a verb+resource an agent can act on. The title 'Sensitive Points' is simply restated in jargon.

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 named anywhere in the description, despite nine sibling cosmobiology tools covering overlapping techniques. Only the bracketed group tag hints at the domain, which is not usage guidance.

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