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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds genuinely useful trust semantics — the definition of the verified field (bundled manifest recomputes to the pinned root hash, attestation matches the build-time digest) and version-dependent content (contract 1.4.0 adds plug record basis with DOCUMENTED_FACT/INFERENCE/UNKNOWN labels). That is real value beyond annotations, but the rest is a field inventory rather than 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?

The first sentence is a ~100-word run-on that enumerates nearly every field of the response, most of which the output schema already documents. The one genuinely non-obvious fact — the meaning of verified and the contract-1.4.0 conditional content — is buried at the end instead of being front-loaded.

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 an output schema present, return values need no explanation, yet the description spends most of its length on exactly that. What an agent actually lacks — when to call this versus verify_publication or get_plug_record — is never addressed, so the definition is complete on data shape but incomplete on routing.

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 the baseline is 4. There is nothing to disambiguate, and the description correctly does not invent parameter guidance.

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 opening clause names a specific verb and resource: it describes the publication metadata served by this endpoint, and the enumerated fields (root hash, publication id, contract version, source file digest, rule parameters) make the resource concrete. It never distinguishes itself from the sibling verify_publication, whose subject matter it partly overlaps, 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 explicit when-to-use or when-not-to-use statement, and no named alternative among the eight siblings. The sentence about the verified field implies the tool also reports verification status, which makes the overlap with verify_publication more confusing rather than resolving it.

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