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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is covered. The description adds the credit cost ('10 credits (Tier 1)'), which is useful behavioral context, but it does not address determinism/seed reuse, whether generation is idempotent, or whether a second call re-charges credits.

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?

The text is dense and front-loaded: the dispatcher scope and the enum of types come first, then the conditional-required rules. The trailing ellipsis ('seed …') indicates it is cut off, so it is not maximally efficient, but there is little filler.

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 no explanation, and annotations cover the safety profile. Against 13 parameters at 38% coverage, though, the description only partially compensates, and being truncated it leaves the caller without the full picture of how the 12 modes differ in required inputs.

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 coverage is only 38%, so the description carries extra burden. It does add real value by explaining the conditional requiredness the schema cannot express (chart for most types, chart1+chart2 for synastry), but the text is truncated mid-sentence and leaves the remaining parameter interactions (seed, whitelabel, fields/precision compact mode) unaddressed.

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 states a specific verb and resource ('Single endpoint over the 12 type-specific renderers') and enumerates the 12 report_type values, so an agent immediately understands this is the unified dispatcher. It distinguishes itself conceptually from the type-specific siblings ('over the 12 type-specific renderers') but never names them or contrasts call patterns 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?

It gives substantive conditional guidance on inputs ('Required fields vary by type: chart for most, chart1+chart2 for synastry, seed …'), which is genuine when-to-use value. However, it offers no explicit guidance on when to call this dispatcher versus the individual astroway_reports_natal / _synastry / _business tools in the sibling list, which is the central routing decision for this tool.

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