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

Annotations only declare readOnlyHint=true, so the description carries the real burden and does it well: it warns that all returned text is untrusted, that labels are advisory and their absence is not evidence of safety, and that signed records pass through unmodified with labels delivered via a content_labels[id] sidecar. This is exactly the kind of trust-boundary context an agent cannot get from structured fields.

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?

Six short sentences, front-loaded with the resource and scope before trust caveats and delivery semantics. Dense but each sentence carries a distinct idea; the sidecar sentence is long but earns its place given there is no 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?

For a two-parameter read tool with no output schema, the description covers the trust model, default vs opt-in label filtering, and where labels surface in the response. The only omission is the meaning of limit, which is minor relative to 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 coverage is 50%: exclude_labels is fully documented in the schema (categories, max three, no duplicates, omit for label-only), making the description's restatement largely redundant, while limit (1-30) is documented nowhere. The description adds no syntax or meaning for limit, so it neither compensates for the gap nor goes beyond the schema.

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?

Opens with a specific verb+resource ('Read deterministically compiled research packets') and enumerates the packet kinds it covers (proposal, feedback, criticism, synthesis, maturity, single-origin warnings). It also draws a scope boundary ('Not scientific validation'), which helps distinguish it from validation-oriented siblings, though no sibling is named explicitly.

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?

The description never says when to reach for this tool instead of research_core, knowledge_search, or validation_standards. The only conditional guidance is about parameter behavior ('Default is label-only; exclude_labels explicitly opts into filtering'), which is invocation mechanics rather than tool selection.

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