proxychains_remove

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

No annotations are present, so the description must convey behavioral traits. It only says 'Remove a proxy from the chain' without disclosing persistence, error behavior, or effects on active connections. It also does not clarify what happens if multiple proxies match the host:port criteria.

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 of 12 words with no redundancy. It is efficient, though slightly more detail (e.g., clarifying '0-indexed') could be added without sacrificing conciseness.

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 removal tool with no required parameters and no output schema, the description covers the essential functionality. It does not address edge cases like removing a non-existent proxy or returning confirmation, but these are minor omissions.

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 coverage is 100%, so the baseline is 3. The description adds value by summarizing the two identification methods ('by index or by host:port'), which maps to the parameters. However, it does not explain that port is required when using host, nor that index is 0-indexed (though schema describes that).

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 the action ('Remove') and the resource ('a proxy from the chain'), and specifies two distinct methods of identification (by index or by host:port). This distinguishes it from siblings like proxychains_add or proxychains_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?

No guidance is provided on when to use this tool over alternatives (e.g., proxychains_edit or proxychains_config) or when to prefer removal by index versus host:port. The agent must infer usage from context.

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