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 safety is covered. The description adds genuinely useful non-annotation context: the endpoint path and the cost of 10 credits (Tier 1). It says nothing about computational behavior or the effect of the domain-specific flags (withTnp, cosmogram), leaving that gap.

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 and front-loads the domain phrase, but the bracketed metadata blocks partly duplicate structured data (required params, group) rather than adding meaning. Every sentence technically 'earns its place' only in the cost and endpoint lines; the core prose is too thin to be efficient.

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 astrological calculation, the description omits what sensitive points are, how they differ from sibling midpoint tools, and how the non-obvious flags change results. An output schema exists so return values need no explanation, but that does not cover the usage and parameter gaps, which remain substantial.

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, so the description must compensate and does not. It lists the four required params (date, time, latitude, longitude), which the schema already enforces, and says nothing about the many undocumented params: withTnp, cosmogram, zodiacType, houseSystem, ayanamsaId, name, city. No syntax, defaults, or interaction guidance is added.

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 prose is a single noun phrase, 'Ebertin's personal points midpoint hits,' which names a domain-specific artifact but no verb or output. It does not distinguish this tool from close siblings such as astroway_cosmobiology_personal_point_tree, midpoint_pictures, or transit_midpoints. An agent outside Hamburg School astrology cannot infer what is computed or returned.

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?

No when-to-use, when-not-to-use, or alternative routing appears anywhere. The '[Required: ...]' block merely restates the schema's required list and is not usage guidance. Nothing tells the agent why it would pick this over the other cosmobiology endpoints.

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