查看数据源状态

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?

输入模式无参数，描述无需补充参数信息，符合基线4分。

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?

描述明确说明'查看多数据源的状态和熔断器信息'，动词和资源清晰，与众多股票交易工具区分明显。

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.