mh_tools_list

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

No annotations are provided, so the description must carry the burden. The description only states what it lists but doesn't disclose any behaviors like whether it requires authentication, whether it returns stale data, or whether it makes external calls. It doesn't contradict anything, but it's thin on behavioral context.

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 a single sentence in Chinese, which is concise and to the point. It front-loads the purpose ('列出全部预生成答案工具') and adds the extra detail (freshness). It could be slightly more structured but it's efficient.

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 listing tool with no parameters, the description provides the essential what (list) and the extra (freshness). It doesn't describe the output format, but since there's no output schema, the description might need to hint at what 'freshness' means, but it's not critical. It's minimally complete.

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?

With zero parameters, the description doesn't need to explain parameter semantics. The schema is empty, and the description correctly avoids mentioning parameters. A baseline of 4 is not necessary because there's nothing to compensate for.

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 purpose: listing all pre-generated answer tools and providing freshness information. It is clear about the resource (pre-generated answer tools) and the action (list). It doesn't explicitly distinguish from siblings, but the siblings have different names suggesting different functions.

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 implies when to use it (when you need an overview of available pre-generated tools and their freshness), but it doesn't explicitly state when not to use it or mention alternatives. For a tool with no parameters, context is limited, so a 3 is reasonable.

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