remote_profile_delete

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=false, so the description's only job is to add context — yet it adds nothing. It does not say whether deletion is permanent, whether the profile must be inactive, what happens if the name does not exist, or whether related sessions/credentials are affected.

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?

A single short sentence with no wasted words and the destructive verb front-loaded. Its brevity is efficient rather than padded, though it borders on under-specification.

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?

The presence of an output schema and full annotation coverage reduces the burden, but for a destructive single-parameter tool with 0% parameter coverage, the description should at least clarify the identifier semantics and the permanence of deletion. Neither is provided.

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?

There is one parameter at 0% schema description coverage: 'name' carries only a type, no meaning. The description never explains that this is the profile name, whether it is case-sensitive, or whether it must match an existing profile exactly, so the single undocumented parameter is left entirely ambiguous.

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?

States a specific verb ('Delete') and resource ('saved connection profile'), which an agent can easily distinguish from sibling operations like remote_profile_rename, remote_profile_create, or remote_profile_update. However, it does not explicitly reference any sibling to sharpen the boundary.

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?

No guidance on when to use this versus alternatives such as remote_profile_rename or remote_profile_update, and no prerequisites or cautions are stated despite the operation being destructive.

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