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

Annotations already cover the safety profile: readOnlyHint=true, idempotentHint=true, openWorldHint=false, destructiveHint=false. The description adds useful operational context such as the POST endpoint and 10-credit cost, but it does not disclose auth needs, rate limits, or return behavior beyond what the output schema provides. The POST endpoint does not contradict the read-only annotation.

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 very concise: one symbolic line followed by clearly structured metadata (group, endpoint, cost). It is front-loaded and wastes little space, though the main line is a fragment rather than a full operational statement.

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 no-required-parameter tool with a rich output schema and safety annotations, the description plus structured fields is close to callable. However, it still omits what the operation actually does or returns, and it provides no selection context relative to sibling geomancy figures.

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 both optional parameters ('fields' and 'precision') are fully documented in the input schema. The description adds no additional parameter semantics, so the baseline score of 3 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 names the specific geomantic figure and gives its symbolic meaning, but it never states the operation the tool performs (e.g., returns/retrieves a Cauda Draconis reading). It is identifiable as a geomancy figure tool, yet the purpose remains vague at the action level.

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 explicit when-to-use guidance and no mention of alternatives among the many geomancy sibling tools. 'Endings, exit' is symbolic meaning, not an instruction about when this tool should be selected.

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