use_profile

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains that the tool disconnects the old adapter and creates a new connection using profile.config, notes the historical bug fix, and states that the returned connection field reflects the new state. This is meaningful behavioral context beyond the basic purpose.

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: two sentences that state the primary purpose, describe the actual behavior, and mention the return field. The bug-history note adds useful context without unnecessary padding.

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 one-parameter tool with no output schema and no annotations, the description covers the main action, the underlying behavior, and the return value. It does not discuss error cases or prerequisites, but the core information needed to invoke the tool successfully is present.

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 0% and the only parameter 'name' is just a string. The description indicates that the name refers to an already-saved profile, which adds some semantic meaning, but it does not clarify naming rules, behavior when the profile is missing, or whether the name is case-sensitive.

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 opens with a specific verb and resource: '切换活跃连接到已存 profile' (switch active connection to a saved profile). It clearly identifies the tool's action and distinguishes it from sibling tools like create_profile or enable_profile by focusing on switching the active connection.

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 implies the tool is for switching to an existing profile, but it does not explicitly state when to use it versus alternatives such as enable_profile, disconnect_profile, or get_active_profile. No when-not-to-use conditions or exclusions are provided.

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