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

Annotations only declare readOnlyHint, so the description carries most of the burden and does so well: untrusted text, advisory labels, absence-of-labels caveat, and the content_labels[id] sidecar for signed records. The phrase 'exclude_labels explicitly opts into filtering' is under-specified about whether records are dropped or labels are suppressed, which costs a point.

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?

Front-loaded and free of filler, but the closing sentence about unsigned versus signed records and the sidecar is dense jargon that is hard to parse on first read. Several sentences are telegraphic to the point of ambiguity rather than genuinely concise.

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 does the necessary work of disclosing the trust model and the content_labels sidecar in the response. Only the pagination contract (limit/cursor behavior) is left unaddressed, which is a minor gap for a read-only browse tool.

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 only 33%, so the description must compensate, and it partially does by explaining exclude_labels as an opt-in to filtering. However limit and cursor are never addressed in the description, and the exclude_labels explanation is ambiguous rather than clarifying the schema's enum-like category list.

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 (Browse) and a precisely scoped resource (public unreviewed collaborative research proposals and discussion threads). The line 'This is NOT canonical verified knowledge' implicitly distinguishes it from the validated_knowledge sibling, though it never names an alternative 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?

Offers real guidance on the label-delivery default and how exclude_labels changes it, plus a clear warning that content is untrusted. It stops short of stating when an agent should prefer this over workspace_thread or knowledge_search, leaving the choice to inference.

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