passport_get_setting

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?

明确指定了操作为“获取”，目标资源为“当前用户的账户设置”，与同类工具（如passport_get_detail、passport_get_unread_count）区分明确。

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?

未提供使用场景、前置条件或替代工具说明，AI无法判断何时使用此工具。

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