calculate_kundali

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

No annotations are provided, so the description carries the burden. It states the tool is a 'Preview' implying read-only, but doesn't disclose authentication needs, rate limits, or what happens on invalid input. Basic transparency is present but incomplete.

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 sentences efficiently convey purpose, outputs, and limitations. Front-loaded with verb and resource.

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?

For a preview tool with 5 parameters and no output schema, the description covers inputs, outputs, and a limitation (full chart on website). It is suitable for the tool's scope, though error handling and output format are omitted.

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 baseline is 3. The description adds little beyond the schema (e.g., latitude examples are in schema). It does not explain the ayanamsa options or how parameters affect the output.

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 the tool previews a Vedic birth chart and lists specific outputs (Lagna, Sun/Moon sign/house, Nakshatra, Dasha). It differentiates from siblings (get_nakshatra, get_panchang) by focusing on the full chart preview rather than specific elements.

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 implies usage for a birth chart preview and notes that the full chart is available on a website, providing a boundary. However, it lacks explicit when-to-use vs siblings or when-not-to-use guidance.

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