Generate Vedic Kundli (PDF or HTML)

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

Annotations are light (not read-only, not destructive). Description adds credit cost and output format, but does not discuss side effects (e.g., data storage, rate limits). No contradiction with annotations.

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?

Two concise paragraphs plus example. Front-loads key astrological content and cost. Every sentence adds value; no fluff.

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?

Covers core purpose, content, and cost. Lacks output format detail (no output schema) and explicit guidance for selecting among sibling tools. Example helps but is not comprehensive.

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 33% (only chart has description). The tool description adds an example but does not explain the language enum or the whitelabel object, leaving many parameters underspecified.

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 generates a Vedic Kundli (PDF or HTML) with specific content (Lagna, Moon nakshatra/pada, planet positions, Vimshottari Dasha). It distinguishes from Western chart tools but does not explicitly differentiate among the many sibling report tools.

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?

Includes cost warning and instruction to confirm with user, plus an example request. However, no guidance on when to use this tool versus alternative reports or vedic tools, and no prerequisites mentioned.

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