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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful operational context beyond the annotations: the group ('Geomancy (Agrippa)') and the cost ('10 credits (Tier 1)'). It still says nothing about the output form or whether the result is static, but the cost disclosure earns partial credit.

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?

It is short and the operative theme is front-loaded, with metadata tagged at the end. However, the extreme terseness reflects under-specification rather than economy: the text is too thin to convey purpose or routing, so the brevity does not fully 'earn its place'.

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?

The tool is simple: two optional formatting params, full schema coverage, an existing output schema (so return values need no explanation), and annotations covering safety. Against that low complexity a minimal description is tolerable, but the total lack of differentiation from fifteen sibling figure tools leaves an agent unable to route to this tool confidently.

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 parameters (fields, precision) are fully documented in the schema with usage examples and defaults. The description adds no parameter semantics at all, so the baseline of 3 applies given the schema carries the full burden.

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 gives only thematic keywords ('Movement, change, journey') that restate the esoteric meaning of the name/title 'Via: The Way' rather than stating what the tool does. There is no verb and no resource, so an agent cannot tell whether it returns an interpretation, a chart, or a lookup. It also fails to distinguish this tool from its fifteen near-identical geomancy siblings (puer, albus, laetitia, etc.).

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, no prerequisites, and no mention of any alternative. With fifteen structurally identical geomancy figure tools listed as siblings, the absence of any selection criteria is a serious gap. Nothing tells the agent when 'Via' is the right figure vs. any other.

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