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

Annotations already declare readOnly, idempotent, closed-world, non-destructive behavior, so the safety profile is covered. The description adds meaningful behavioral context beyond that: the deterministic pipeline, supporting vs opposing evidence, uncertainty handling, and explicit abstention boundaries. It omits any note on auth, rate limits, or latency, so it is not a full 5.

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?

Three tightly written sentences, front-loaded with the core action before the return contents. The closing sentence about the web app sharing the engine is low-value framing but brief, so little is wasted.

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 detail is not strictly required (and the description arguably over-covers it). But with 12 parameters at 0% coverage and no sibling differentiation, the definition leaves real gaps for an agent deciding how to invoke it versus its many analyze_* neighbors.

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 0% across 12 parameters, so the description carries the full burden of explaining them — and it does not. It never mentions the required date/time pair, the place-vs-coordinates anyOf, timezoneOffset, language, or birthTimeAccuracyMinutes, and it lists only five of the eight topic enum values.

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?

States a specific verb and resource ('Runs the shared deterministic judgment pipeline') plus the topical scope, and the return ledger is named. However, it does not distinguish itself from close siblings like analyze_career_structure or analyze_education_structure, leaving overlap unresolved. The topic list also omits three enum values (wealth, health, children), which slightly muddies the stated scope.

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, when-not-to-use, or alternative routing. Given siblings such as analyze_house, analyze_varga, and the per-topic analyze_*_structure tools, an agent has no guidance on why it would call this instead of those. Only an implied 'one topic at a time' reading is available.

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