keychain_disconnect

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds useful authentication-scope context by saying the removal is 'Scoped to the caller's UNCLICK_API_KEY,' but it does not describe reversibility or what happens when label is omitted beyond what the schema says.

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 two short sentences with no waste, and it front-loads the core action. Every sentence earns its place by stating the operation and its caller-scoping constraint.

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 two-parameter destructive tool, the input schema fully documents the parameters and the annotations fully declare the safety profile. The description adds the API-key scoping context, though it could be more complete by routing agents away from keychain_connect or keychain_secure_connect.

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 description coverage is 100%, with platform values and the label omission behavior fully documented in the input schema. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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 specific verb and resource: 'Remove a platform credential from the UnClick Keychain.' It also adds scope via the caller's UNCLICK_API_KEY, but it does not explicitly differentiate itself from sibling tools like keychain_connect or keychain_secure_connect.

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 says what the tool does but gives no explicit guidance on when to use it versus alternatives such as keychain_connect, keychain_secure_connect, or keychain_status. It also does not state prerequisites or when-not-to-use conditions.

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