Generate Business Astrology Report (PDF or HTML)

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

Annotations indicate the tool is not read-only (readOnlyHint=false), not destructive, and not idempotent. The description adds a disclaimer and notes it's a premium report, but does not explain behavioral details like what happens after generation (e.g., storage, deletion). The cost note is helpful but not behavioral.

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 description is three focused sentences plus a formatted cost warning. It is front-loaded with purpose and key content highlights. The example and group tag are separate, keeping the core concise. A fifth sentence might be warranted for output format details, but current structure is efficient.

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?

No output schema exists, so the description should clarify the report format (PDF/HTML) and structure. The title hints at formats, but the description omits this. The cost warning and disclaimer are present, but missing details on what the generated report contains (e.g., page count, sections) reduces completeness.

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 100%, so the baseline is 3. The description does not add meaning beyond the schema; it simply references chart data. The example request body provides a concrete usage pattern, but this is not part of the description itself.

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 performs founding-chart analysis for business, highlighting specific planetary points (Sun, MC, Jupiter, Saturn). The title adds that it generates PDF or HTML output. This distinguishes it from other report tools (e.g., reports_natal, reports_synastry) by focusing on business astrology.

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 description lacks explicit guidance on when to use this tool vs. alternatives. A cost warning is present but not usage context. Given many sibling report tools, the description should indicate what scenarios call for a business report vs. a natal or synastry report.

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