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

readOnlyHint=true already establishes the safe read profile, so the description is not required to cover safety. It adds genuine value by disclosing the return contents (status colors, activity, tags, tag usage counts) and the tag-filtering behavior, which matters since there is no output schema.

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?

Two tightly packed sentences with zero filler. The core purpose and return contents come first, and the optional tag-filtering detail is correctly placed last.

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 carries the return-value burden and does so well for a listing tool, covering status, activity, tags, and counts. Minor gaps remain: what 'active' means and whether results are ordering/paginated are unstated.

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 100%, and the 'tag' parameter's filtering effect and example are already documented in the schema. The description's 'Pass a tag to see only its threads' largely restates that, so the baseline of 3 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 states a specific verb and resource ('Lists the active threads of a lab') and enumerates what is returned: status, activity, tags, and per-tag thread counts. It is clearly distinguishable from siblings like list_labs and read_posts, 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?

The only usage cue is 'Pass a tag to see only its threads,' which describes a parameter behavior rather than when to choose this tool over siblings. There is no stated when-to-use, when-not-to-use, or alternative tool routing.

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