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

Annotations only say this is a non-read-only, non-idempotent, open-world call. The description adds material behavioral context the annotations lack: the exact credit cost, its share of the free monthly budget, and the requirement to confirm before invoking. It omits the PDF-vs-HTML output distinction implied by the title, which is a notable gap.

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 report's identity and content in two sentences, then the cost warning. Efficient and well ordered, though the 'includes full natal data and a disclaimer' clause is closer to filler than actionable detail.

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 described, and the cost/confirmation guidance is a real addition. But for a five-parameter premium report tool, the absence of any input guidance and the missing PDF/HTML output clarification leave the definition incomplete for confident invocation.

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 only 60%, so the description is expected to compensate, yet it mentions none of the five parameters (chart, fields, language, precision, whitelabel). Everything an agent learns about inputs comes from the schema, and the description adds zero parameter meaning.

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 output — a parenting-oriented natal report — and enumerates its content (Moon, Mercury, Venus, Mars, full natal data, disclaimer). The 'child'/'parenting-oriented' framing implicitly distinguishes it from the sibling astroway_reports_natal, though it never explicitly says to prefer this one for a child's chart.

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 premium cost block gives a genuine usage instruction (5,000 credits, ~50% of the free monthly budget, confirm with the user first), which is useful operational guidance. However, there is no statement of when to choose this over astroway_reports_natal or other report siblings, so selection guidance remains implied.

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