credential_profile_delete

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

The description adds valuable context beyond the destructiveHint annotation by clarifying exactly what is NOT deleted (ssh-agent keys, private-key files, Git Credential Manager credentials). This precisely scopes the destructive behavior, which is important for a delete operation.

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 concise sentences, front-loaded with the action and immediately followed by a crucial clarification. No unnecessary words or repetition.

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 single-parameter delete tool with destructive annotations, the description adequately covers the core purpose and scope of deletion. However, it lacks any explanation of the 'id' parameter or how to find the profile ID, which is a minor gap given the tool's simplicity.

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 0%, so the description must compensate for the 'id' parameter. It does not explicitly explain what 'id' refers to or how to obtain it (e.g., from credential_profile_list). The meaning is only inferred from the tool name, which is insufficient for a low-coverage 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 clearly states 'Delete one RunBeacon credential reference profile' with a specific verb and resource. This distinguishes it from sibling tools like credential_profile_save, credential_profile_list, and other delete tools such as ssh_password_delete and github_token_delete.

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 provides clear context by explaining that this tool only deletes the reference profile, not underlying credentials, implying it should be used when you want to remove the profile without affecting stored credentials. However, it does not explicitly name alternative tools or provide when-not-to-use scenarios.

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