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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered. The description adds no behavioral context beyond the geometry — nothing about the SVG/JSON output, theming, size limits, or credit consumption beyond the bracketed cost tag.

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 front-loaded sentences with no filler, followed by compact group/cost metadata tags. Nothing is wasted, though the extreme brevity is part of the guidance gap rather than a virtue in itself.

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 and the input schema is exhaustively documented, so return values and parameters need no prose. However, for a render tool sitting among thirteen sibling renderers with a large options surface, the description does not supply the selection or usage context an agent needs.

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 100%, so the baseline is 3; the deeply documented body, options, fields and precision parameters already carry all meaning. The description contributes nothing about any parameter, including the fact that output is JSON by default rather than SVG despite the title.

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?

States a specific verb ('Plots') and a well-defined resource ('Cosmobiology 90° dial'), then explains the distinguishing mechanic — longitudes reduced mod 90 and Cardinal/Fixed/Mutable repeated across four quadrants. That is enough to tell it apart from a plain Western wheel, though it never names or contrasts a sibling explicitly.

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 guidance on when to pick this renderer over the other dozen astroway_render_* tools, no mention of when a cosmogram is the appropriate visualization, and no note on choosing format=svg vs json. The reader is left to infer everything from the title.

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