Lal Kitab — Kundali (12-house grid)

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

Annotations already indicate readOnlyHint=true and idempotentHint=true, so the description adds value by specifying that the output includes 12 houses with planets and state. 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?

The description is concise with two main sentences, a group tag, and an example. It is front-loaded with key information and has no unnecessary words.

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?

Given no output schema, the description provides a basic understanding of the output (12 houses with planets and state). However, it lacks details about the 'state' meaning, error handling, or parameter descriptions, which would improve completeness for a complex tool with 11 parameters.

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 0%, so the description must compensate. It provides an example request body with 5 parameters, but does not explain the meaning or format of the 11 total parameters. The example is helpful but insufficient for understanding the full parameter set.

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 identifies the tool as a Lal Kitab kundali grid layout with 12 houses listing planets and their states. It distinguishes itself from sibling tools by specifying 'Lal Kitab' and the grid format, and mentions it is a companion to /teva for chart visualization.

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 states it is a companion to /teva for chart visualization, providing context on when to use this tool vs the sibling teva tool. However, it does not explicitly state when not to use this tool or mention alternatives among the many sibling tools.

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