tcp_proxy_delete

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

No annotations provided, so description carries burden. Indicates permanent deletion via 'Not for: Temporary proxy disabling', but lacks details on reversibility, cascading effects, or confirmation. Still sufficient.

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?

Description is concise with bullet points and emojis, front-loads purpose, and uses clear sections. Every sentence adds value.

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 one required parameter, no output schema, and straightforward behavior, the description covers key aspects: purpose, usage guidelines, prerequisites, and related tool.

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% and already describes proxyId as 'ID of the TCP proxy to delete'. Description adds no extra semantics beyond that. Baseline 3 applies.

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?

Description clearly states 'Delete a TCP proxy' with specific verb and resource. Best for section reinforces purpose and distinguishes from siblings like tcp_proxy_create and tcp_proxy_list.

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?

Explicitly lists when to use (Removing unused proxies, Security management, Endpoint cleanup) and when not (Temporary proxy disabling, Port updates). Also mentions prerequisites (tcp_proxy_list) and related tool (service_update).

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