Vedic Wheel — South Indian (SVG)

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

Annotations (readOnlyHint, destructiveHint, idempotentHint) already indicate a safe read-only operation. The description adds minor context about the layout but does not significantly enhance transparency beyond the 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 short and includes a group tag and an example. However, the example is somewhat redundant given the schema, and the description could be more concise by omitting it.

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?

The description is minimal for a tool with many sibling tools and a complex schema. It lacks details about the output format (SVG), how to configure options, and what the tool returns, leaving the agent with insufficient context to use it properly.

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 description does not add new parameter details beyond the schema. The example request body is present but adds no semantic value over the schema's description.

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 renders a South Indian Vedic wheel in a 4x4 grid with fixed signs, and mentions house number placement. However, it does not distinguish from sibling tools like render_wheel_vedic_east or render_wheel_vedic_north, which are similar in purpose.

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?

No guidance on when to use this tool versus alternatives such as other Vedic wheel renderings or render_aspect_grid. The description simply describes the layout without providing usage context.

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