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

Annotations cover the safety profile (readOnly false, destructive false, openWorld true, idempotent false), so the bar is lower, and the description still adds materially: it discloses the deterministic non-AI rendering behavior and a concrete cost of 5,000 credits (~50% of a free monthly budget) requiring user confirmation. It does not say what is required for the call to succeed (e.g. a valid chart object) or how the artifact is delivered.

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?

Front-loaded with the concrete deliverable and its visual contents, with no filler sentences. It loses a point because the style enumeration is cut off mid-word in the third option, leaving the structure visibly incomplete.

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 values need not be explained, and cost/tier is disclosed. But the title promises 'PDF or HTML' while neither the description nor the schema exposes any format selector, and the third style value is truncated — so an agent cannot fully determine the call's output mode from the description.

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 50%, so the schema carries most parameter meaning, including the detailed chart/timezone/houseSystem notes. The description adds value only for `style`, enumerating editorial (light) and celestial (dark + gold) and starting a third ('cl…', presumably classic) that is truncated. `fields`, `precision`, `language` and `whitelabel` are left entirely to the schema.

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 and resource ('Render a data-rich, print-ready natal chart poster') and enumerates the visual contents (wheel, Sun/Moon/Rising trio, placements table, balance bars, aspects), so the output is unambiguous. It differentiates itself implicitly from the narrative report siblings by being a deterministic chart render with '0 AI'. However it never names a sibling or explains how it differs from astroway_reports_natal or astroway_reports_generate.

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?

Usage is implied by the content list and the cost banner ('Confirm with user before invoking'), which is genuine invocation guidance. But there is no explicit when-to-use framing, no exclusion rules, and no pointer to the alternative report tools an agent should pick instead for a written interpretation.

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