set_settings

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

With no annotations provided, the description carries the burden and does disclose important behavioral traits: enabling send affects all Bots under the account, confirmation cards are required for send and allow_sensitive, and authorization codes must not be written into the tool. It stops short of explaining persistence, reversibility, or the confirmation-card return flow, and '打开草稿' is somewhat ambiguous.

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 compact and front-loads the main purpose, then gives mode-specific conditions, a security warning, and scope. Every sentence adds useful information, though terms like '档位' and '打开草稿' reduce precision and clarity.

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 simple three-parameter tool, the description covers core modes, prerequisites, security, and scope, which is fairly complete. However, it omits the mode=read case, does not explain the confirmation-card flow or return behavior, and does not route the agent to sibling tools like get_settings when read-only access is needed.

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 coverage is 100%, so the baseline is 3, but the description adds conditional semantics beyond the schema: mode=send requires send_allowlist plus confirmation, and allow_sensitive requires confirmation. It explains mode=draft behavior, though mode=read is never addressed and send_allowlist syntax is correctly left to the 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?

The description states a clear action ('修改' / modify) and targets ('档位' or mode, and send allowlist), and it is clearly tied to the set_settings resource rather than get_settings. However, '档位' is an ambiguous way to refer to the 'mode' parameter, and '在用户选定后' adds context without explaining what selection means.

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 gives explicit conditional usage rules: mode=draft opens draft mode, mode=send requires send_allowlist and a confirmation card, and allow_sensitive also requires confirmation. It does not mention alternatives or when-not-to-use conditions, but the mode-specific guidance is clear and actionable.

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