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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful operational context the annotations do not: the endpoint (POST /v1/geomancy/populus) and the cost (10 credits, Tier 1). It says nothing about what the reading contains or whether any prerequisites apply.

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?

Very short and front-loaded with no filler prose, and the bracketed metadata block is easy to scan. However, the brevity comes from under-specification rather than discipline — the keyword list occupies the place where purpose should be.

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 documentation is not required, and annotations cover the safety profile. But for a divination endpoint whose entire value is the meaning of the Populus figure, the description gives no indication of what a caller receives or how this figure's reading differs from its many siblings.

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 documented there with examples and rationale. The description adds no parameter meaning of its own, 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?

The description is a bare keyword gloss of the figure's meaning ("Crowd, gathering, public") and simply restates the name and title. It never states a verb or what invoking the tool actually returns — a reading, an interpretation, a cast figure — so an agent cannot tell what the tool does beyond the word 'Populus'.

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 differentiation from the 15 sibling geomancy figures (Puer, Puella, Via, Rubeus, etc.) that share the identical pattern. An agent has no signal for choosing Populus over Albus or Coniunctio.

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