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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the description does not contradict it. The description adds genuine non-annotation behavior in the credit cost (10 credits, Tier 1) and the POST endpoint, but says nothing about auth requirements, rate limits, or that output can be SVG or JSON per the format option.

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 substantive sentence is front-loaded and zero-waste, and the metadata block is compact and scannable. It is arguably too terse rather than bloated, but nothing in it is redundant with the structured fields.

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 render tool with a large options object (theme, size, labels, bodies, format) and two near-identical siblings (vedic_north, vedic_south), the most important missing context is how to choose among the three Indian layout variants. The output schema excuses it from explaining return values and cost is given, but the selection-critical gap against its siblings is left entirely to the reader.

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%, so the schema already documents the body, fields, precision, timezone, ayanamsa and label options in detail. The description adds no parameter meaning beyond what the schema provides, which is the baseline-3 case when structured fields do the heavy lifting.

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 names the specific layout variant (East Indian/Bengali, square with diagonals plus an inner rotated square forming 12 sectors), which is the one thing that visually separates it from the vedic_north and vedic_south siblings. It never states the verb ('render a chart wheel') explicitly, but the tool name and title carry that, so the combined signal is clear.

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 when-to-use guidance at all: nothing says to pick this when the user asks for an East Indian/Bengali style chart, and no alternative (vedic_north, vedic_south, western wheel) is named or contrasted. The only routing context is the [Group: Visualization] tag, which is structural rather than advisory.

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