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 fully covered by structured data. The description adds genuine context beyond that — the '[Group: Geomancy (Agrippa)]' taxonomy and the '[Cost: 10 credits (Tier 1)]' billing tier — but says nothing about what the response contains or any auth/quota behavior.

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 front-loads the figure's semantic keywords before the bracketed metadata, with no wasted sentences. However, it is under-specified rather than genuinely concise — the terseness leaves the operation undefined.

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 values need not be explained, and annotations fully cover the safety profile with zero required parameters. The remaining gap is the missing statement of what the tool actually produces, which is significant but partly mitigated by the structured fields carrying the rest.

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% for both optional parameters (fields, precision), and their schema descriptions are detailed and self-sufficient. The tool description contributes nothing about parameters, 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 dump ('Crowd, gathering, public') that restates the title 'Populus: The People' rather than stating a verb+resource operation. It never says what calling the tool does (e.g., returns the Populus geomantic figure and its reading), so an agent cannot tell it apart from the other fifteen astroway_geomancy_* figure tools on anything but the name.

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 or when-not-to-use guidance, no mention of alternatives among the geomancy siblings, and no indication of what question or context should trigger this figure. The only contextual metadata is group and cost, which is not usage guidance.

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