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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed world, so the safety profile is covered. The description adds two pieces of real behavioral context beyond that: the findings are cross-checked against the ledger at build time (i.e., a snapshot, not live), and caveats ship in the same object and should be quoted with the findings. It still says nothing about size, cost, or staleness cadence.

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?

One long run-on sentence dense with capitalized in-house terminology. It is front-loaded with the corpus scope, which is good, but the enumeration of bundled sections reads as a jargon pile rather than a structured list, and several items would be clearer as separate sentences or bullets.

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?

With no output schema, the description usefully compensates by enumerating what the returned object contains and by flagging that caveats travel with the findings. Nothing about the return shape is left wholly unstated, though the individual section names remain undefined.

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?

The tool takes zero parameters, so there is no parameter semantics for the description to carry. Baseline of 4 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 identifies a specific resource — the deep-pass signature findings over the full corpus, cross-checked against the ledger at build time — and enumerates the sections it bundles (mechanism ledger, war read, named-before-the-event register, warnings, counterfactual, routing lane). However, it is a noun-phrase content dump without a clear action verb, and it never distinguishes itself from closely related siblings such as get_calibration_and_integrity, get_information_yield, or search_sealed_forecasts, so an agent must infer the boundary.

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 guidance, no when-not-to-use, and no named alternative among the twelve siblings whose scopes overlap. The description only says what is inside, leaving the agent to guess at selection criteria.

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