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

Annotations already cover the safety profile (read-only, idempotent, closed-world), so the bar is lower. The description still adds real behavioral context beyond them: it declares the pipeline deterministic, enumerates the evidence artifacts (supporting/opposing evidence, Varga confirmation, Dasha activation, uncertainty, citations, unresolved source keys) and, importantly, explicit abstention boundaries.

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 sentences, front-loaded with the core action, then the return contents, then a brief positioning line. Mostly efficient, though the enumerated return list is a dense dump that partly duplicates the output schema.

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 restated, yet the main gaps remain: no routing guidance versus the topic-specific siblings and no parameter semantics for 12 params at 0% schema coverage. It is adequate for a generic pipeline but leaves the agent under-informed.

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 must compensate and largely does not. It only gestures at the topic values and even omits 'wealth'; it says nothing about name/date/time/place vs lat-long/timezone alternatives, asOfDate, language, or birthTimeAccuracyMinutes.

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+resource ('Runs the shared deterministic judgment pipeline') scoped to named topics, so the agent knows it produces a topic-level judgment. It does not distinguish itself from the many topic-specific siblings (analyze_career_structure, analyze_marriage_structure, etc.), and it lists five topics while the enum also allows 'wealth', a small inaccuracy.

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 guidance and no named alternative across ~50 siblings. An agent cannot tell whether to call this generic topic pipeline or the dedicated analyze_*_structure tools for the same subject.

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