Vedic Wheel: East Indian (SVG)

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely useful non-annotation context: the POST endpoint and a 10-credit Tier 1 cost. It does not disclose that the output defaults to JSON rather than SVG, nor that full birth data (date, time, lat/lon) is mandatory, which are the behaviors an agent most needs to know.

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 layout description is front-loaded in a single efficient sentence, followed by compact metadata tags. It is tight, though the bracketed tags are mechanical rather than informative prose.

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?

With a rich 100%-covered schema and an output schema present, the description need not restate parameters or return values. The layout description plus cost/endpoint metadata covers the essentials an agent needs for a visualization tool.

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 100% and the nested body schema is exhaustively documented (ayanamsa, timezone, houseSystem, theme, labels, etc.), so the schema carries all parameter meaning. The description adds nothing about parameters beyond the layout concept — baseline 3 is appropriate.

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 states the visual layout ('square with diagonals + inner rotated square forming 12 sectors') and the 'East Indian (Bengali)' variant name, which lets an agent distinguish it from the north/south siblings. However, it never says it renders a chart wheel from birth data — the actual action must be inferred from the tool name and title rather than the description text.

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?

There is no guidance on when to choose the East Indian layout over astroway_render_wheel_vedic_north, _south, or _western, and no prerequisite information. Critically, nothing warns that options.format defaults to 'json', so an agent asking for an SVG (as the title implies) may get JSON unless told otherwise.

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