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

Annotations already establish readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context (POST endpoint, 10-credit Tier 1 cost, group membership), which helps budget-aware routing, but says nothing about return behavior, rate limits, or what a 'transformed' result entails.

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 bracketed metadata block is compact and easy to scan, and nothing is padded. However, the brevity is under-specification rather than economy — the single content sentence carries almost no information, so terseness here works against the tool.

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 divination tool sitting among five sibling I Ching endpoints, the description omits what changing lines produce, how it differs from astroway_iching, and what `seed` controls. An output schema exists so return values need not be described, but the remaining gaps leave an agent unable to confidently choose or parameterize this 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?

The description contributes zero parameter meaning. Schema coverage is 67%, and the uncovered parameter is `seed` (anyOf number|string), whose type ambiguity and purpose are left entirely unexplained; `fields` and `precision` are documented in the schema but the description does not reinforce or clarify them.

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 is a noun fragment, 'Primary + transformed hexagrams,' with no verb and no stated action, so an agent cannot tell it casts an I Ching reading rather than looking up or formatting data. It restates the title's notion of changing lines and adds a hint about output shape, but never distinguishes itself from siblings like astroway_iching, astroway_iching_throw_coins, or astroway_iching_by_question.

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, no exclusions, and no reference to any of the five sibling I Ching tools. The only selection-relevant signal is the embedded cost/tier metadata, which is informational rather than directive.

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