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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely useful non-schema context: the cost (10 credits, Tier 1) and the POST endpoint. It does not disclose anything about output delivery or size limits beyond what the schema carries.

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 short sentences lead with the distinguishing layout traits, followed by compact metadata tags for group, endpoint, and cost. Nothing is padded, though the metadata lines are boilerplate rather than explanatory 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?

An output schema exists, so return-value explanation is not owed here, and the annotations cover the safety profile. The description supplies the chart-style identity and the cost/endpoint context an agent needs before calling; only sibling-selection guidance is missing.

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/options parameters are thoroughly documented in the schema itself. The description adds no parameter-level meaning, so the baseline 3 applies.

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?

States a specific resource (North Indian diamond chart wheel) and its defining traits: 12 fixed positions, signs rotating per ascendant, BPHS standard. This distinguishes it from the sibling Vedic east/south wheels without naming them. A clear verb is absent, but 'rendering' plus the endpoint tag makes the action unambiguous.

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 when-to-use guidance and no routing to the alternatives it sits beside (astroway_render_wheel_vedic_east, astroway_render_wheel_vedic_south). The layout description implies a stylistic choice, but the agent must infer that North vs South vs East is a convention preference rather than getting an explicit rule.

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