列出组件

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?

两句完成，信息密度高，无冗余。

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?

对于单参数列表工具，描述覆盖了功能、返回和过滤，可再补充只读性质，但已足够。

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?

参数category的描述在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?

明确说明列出所有组件并可按类别过滤，返回字段具体，与兄弟工具（获取API/示例）区分清晰。

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.