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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, openWorldHint=true), and the description adds genuinely non-redundant context: a 5,000-credit Tier 7 cost, the warning that it consumes ~50% of a free monthly budget, the required user confirmation, and a 'not financial advice' disclaimer. It stops short of describing output delivery (PDF vs HTML link) or any timeouts/rate limits.

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 short sentences plus a bracketed cost block, front-loaded with the purpose. Every element carries information; no padding or restatement of the title.

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 purpose plus cost are covered. However, the description never states the output medium (PDF/HTML), how the generated report is delivered, or that the `language` and `whitelabel` inputs shape the artifact — meaningful gaps for a premium report-generation tool.

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?

The description mentions no parameters at all. With 60% schema description coverage across 5 parameters, the schema is doing all the work (chart, fields, precision, language, whitelabel) and the description adds nothing to disambiguate required vs optional inputs or the compact-mode fields/precision interaction.

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 description names a specific resource and analytic lens ('Founding-chart analysis (mundane astrology)') and enumerates what the report covers (Sun/purpose, MC/reputation, Jupiter/growth, Saturn/structure). It distinguishes itself from a generic natal report by the 'founding chart' framing, though it never explicitly contrasts itself with the closest siblings (astroway_reports_money, astroway_reports_career, astroway_reports_natal).

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?

The only usage instruction is 'Confirm with user before invoking', which is a cost prerequisite rather than selection guidance. There is no statement of when a business/founding-chart report is the right choice versus astroway_reports_money, astroway_reports_career or astroway_reports_natal.

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