remote_profile_delete

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. It states only 'Delete', which implies a destructive action, but does not mention irreversibility, potential side effects on active sessions or dependent resources, or required permissions. This leaves the agent without important context about the consequences of invoking the tool.

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 a single, front-loaded sentence that contains no filler or redundant information. It efficiently communicates the core function without requiring additional reading.

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?

Given the tool's low complexity—one required parameter and an output schema—the description is minimally sufficient to understand the basic operation. However, the lack of behavioral transparency (e.g., irreversibility) and any usage guidance leaves gaps, making it only adequate for straightforward invocation.

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?

The input schema has one parameter 'name' with no description, and schema description coverage is 0%. The tool description adds only the phrase 'saved connection profile', which provides minimal context that the name refers to a profile, but it does not clarify expected format, uniqueness, or how the name is used for deletion. More detail is needed to compensate for the absent schema documentation.

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 uses the specific verb 'Delete' and clearly identifies the resource as 'a saved connection profile'. It distinguishes this tool from sibling tools like remote_profile_update, remote_profile_rename, and remote_profile_list by making the destructive action explicit.

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 no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. While the action is obvious from the name, the description does not explicitly state scenarios where deletion is appropriate or how it relates to other profile management tools.

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