get_weak_topics

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

無注解提供，描述承擔全部責任。它說明了排序方向和包含答對率，但未說明數據來源、是否需要登入、返回格式或任何副作用。對於一個檢索型工具，行為揭露不足。

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?

描述非常簡短，一句話完成，沒有冗餘。但簡短導致資訊不足，未達到適當的規格程度，因此僅給3分。

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?

有輸出schema，但描述未解釋返回結構。參數未說明，使用情境未提供，整體對於一個3參數工具來說不完整。

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描述覆蓋率為0%，描述完全未提及參數（limit、q_type、min_attempts）的含義或用法。描述未補償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?

描述明確指出工具列出考點並按個人正確率由弱到強排序，包含答對率。動詞和資源明確，能與部分兄弟工具（如get_topic_distribution）區分，但未完全排除所有替代工具。

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?

描述未說明何時使用此工具而非其他工具，也未提及任何情境或前置條件。僅陳述功能，沒有使用指引。

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