Generate Natal Report (PDF or HTML)

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

Annotations indicate non-read-only, non-destructive, non-idempotent, open-world hint. The description adds valuable behavioral context: PDF URLs expire after 24 hours via auto-cleanup cron, HTML mode is live, and cost is highlighted. This goes beyond annotations by explaining side effects and longevity, though auth needs are not mentioned.

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?

Description is concise: two sentences with key feature, plus an example and cost warning. It is front-loaded with the main purpose. The cost warning is separated but within the tool definition. No unnecessary words; all sentences add value.

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?

Explains report content and PDF expiry, but does not describe the return format (URL, file, binary?). No output schema exists, so description should specify output. Schema coverage for parameters is incomplete. Example request body is helpful but lacks response example. Additional context like permissions or rate limits is missing.

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 33% (only chart described in schema). The description adds meaning for whitelabel (branding overrides) and hints at language (uk, en) but does not list all 20+ language enum values. The chart object's sub-parameters are partially covered by schema description. Overall, description compensates for low schema coverage but not fully.

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 clearly states it renders a Western tropical natal chart as PDF or HTML, specifying content (Big Three, planets, houses, aspects). The title reinforces 'Generate Natal Report'. However, it does not explicitly differentiate from sibling report tools like reports_business or reports_ai_natal_narrative, leaving ambiguity about when to use this specific tool.

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?

No explicit guidance on when to use this tool versus alternatives. The description lacks 'when-not' conditions or references to similar tools. Siblings include many report tools, but no rationale for choosing this one is provided. A cost warning is present but does not substitute for usage context.

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