Check Thread Health

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

No annotations are provided, so the description carries the full burden, yet it discloses nothing beyond the name: no indication that this is a read-only diagnostic, what 'health' means, what a failing thread implies, or what the result contains. For a health-check tool with zero annotation coverage this is a significant gap.

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 description is only a fragment, so it is short but not by economy — it is under-specified rather than concise. There is no wasted text, but nothing is front-loaded because nothing substantive is stated.

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 and no annotations, the description is the only artifact that could explain the check's result and preconditions, and it supplies none of that. For a diagnostic tool in a dense sibling ecosystem this is insufficient to call the tool correctly.

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?

There is one optional parameter, project_id, with 0% schema description coverage, and the description never mentions it. An agent cannot tell whether the check operates on the active project or requires an explicit project_id, nor what format the id takes.

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 phrase '检查 Meta 线程健康度' gives a clear verb ('check') and a resource ('Meta thread health'), which is more than a tautology of the name. However, it does not distinguish this tool from close siblings such as check_pool_health and check_unresolved_threads, and 'Meta 线程' / '健康度' are not defined here. Adequate but not differentiating.

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 statement of when to use this tool, when not to, or which sibling to prefer for overlapping concepts like thread vs. pool health. The agent must infer usage entirely from the name and the surrounding tool list.

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