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

Annotations already declare the non-read-only, non-idempotent, open-world profile, so the description's job is to add what they cannot. It does that well by disclosing the credit cost, the tier, the share of a free monthly budget, and the requirement to confirm before calling — genuinely decision-relevant behavior. It stops short of billing failure modes or auth expectations, so not a 5.

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 front-loaded with the report's identity and content before the bracketed metadata block, and every line carries information (group, endpoint, required input, cost). The emoji/warning formatting is dense but not padded.

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?

With an output schema present, return values need not be explained, and annotations cover the safety profile; the description fills the remaining high-stakes gap (cost, confirmation, content scope). It is slightly incomplete in that the advertised output formats and the choice against sibling report tools are never addressed.

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 says nothing about any of the five parameters (chart, fields, language, precision, whitelabel); schema coverage is a middling 60%, with language and parts of whitelabel carrying no textual description in the schema either. The one concrete hint, 'PDF or HTML' in the title, maps to no parameter at all, so the description does not compensate for the coverage gap.

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 the artifact ('Parenting-oriented natal report') and enumerates its distinguishing content (Moon, Mercury, Venus, Mars interpretations), which tells an agent this is the child-focused report rather than a generic one. It does not, however, explicitly distinguish itself from close siblings such as astroway_reports_natal or astroway_reports_generate, leaving the agent to infer that distinction from the name.

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 block supplies an invocation precondition — a 5,000-credit Tier 7 cost with an explicit 'Confirm with user before invoking' instruction — which is real usage guidance. But it never states when to choose this report over the numerous alternative report siblings (natal, business, career, synastry), so alternative selection is only implied by the 'child/parenting' framing.

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