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

The annotations already establish that this is a read-only, idempotent, non-destructive, closed-world operation. The description adds meaningful behavioral context by calling it a 'three-question reflective' check and by disclosing the kinds of esoteric outputs returned, while the 'not a diagnosis' line sets an important expectation.

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 two compact sentences with no filler. The purpose and outputs are front-loaded in the first sentence, and the second sentence provides a concise, relevant caveat.

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 low-complexity reflective tool with full annotation coverage and no output schema, the description supplies enough context to understand the tool's purpose and expected result type. It does not explain the optional nature of two of the three parameters or how their inputs affect the result, but the schema covers those details adequately.

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 each of the three enum parameters already has a clear explanation in the schema. The description reinforces the idea of three reflective questions but does not add parameter-level meaning beyond what the schema already provides, so the baseline score 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 a specific verb and resource: a three-question reflective chakra check that suggests an energy center to focus on. It also lists the concrete outputs (theme, element, frequency, affirmation, crystal), making it clearly distinguishable from unrelated siblings such as draw_tarot_cards or bazi_chart.

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?

It gives an intended-use context with 'For self-reflection; not a diagnosis,' which usefully frames when the tool is appropriate. However, it does not explicitly compare this tool with relevant siblings like find_my_crystals or find_healing_frequency, nor does it state when not to use it beyond the diagnosis caveat.

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