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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description does add genuinely useful behavioral context not present in annotations — the cost (10 credits, Tier 1) and the POST endpoint — but says nothing about authorizations, quotas beyond cost, or determinism across calls.

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-loaded, but four of five lines are bracketed boilerplate tags. [Required] duplicates the schema's required array, and [Endpoint] is a value the agent cannot act on. The one line carrying real content — purpose — is the least informative.

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 tool with 31% schema coverage, the definition is thin. An output schema exists so return values need not be explained, but the agent still lacks any picture of what the cosmogram contains, how it differs from dial_90, or what the optional parameters change.

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 merely re-lists the four required parameters (date, time, latitude, longitude), which the schema's `required` array already states, and says nothing about the undocumented optional params (withTnp, cosmogram, zodiacType, houseSystem, ayanamsaId, name, city).

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 body 'Ebertin cosmogram render data' essentially restates the name (astroway_cosmobiology_cosmogram) and title (Cosmogram (90° Render Data)) without adding a verb, output, or scope. It names the domain concept (Ebertin/Hamburg School) but gives no way to tell it apart from siblings like astroway_cosmobiology_dial_90 or astroway_cosmobiology_midpoint_pictures, which are also 90°-dial cosmobiology render tools.

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 routing. The sibling list contains at least a dozen overlapping cosmobiology tools (dial_90, witte_formulas, midpoint_pictures, sensitive_points) and nothing here tells the agent which to pick. The [Required] line is an input constraint, not usage guidance.

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