delete_proxy__id_

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers only the word 'Delete.' This fails to communicate critical information: whether this is permanent or reversible deletion, what permissions are required, whether it affects dependent resources, what happens on success/failure, or any rate limits. For a destructive operation with zero annotation coverage, this is dangerously inadequate.

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 maximally concise with just two words. While this represents severe under-specification rather than ideal conciseness, from a pure structural perspective it contains zero wasted words and is front-loaded with the core action.

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 destructive operation with no annotations, no output schema, and a parameter with 0% schema coverage, the description is completely inadequate. It fails to provide the minimal information needed for safe and correct tool invocation, missing critical context about behavior, parameters, outcomes, and usage boundaries.

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 schema has 0% description coverage for its single parameter 'id,' and the tool description provides no information about what this ID represents, its format, where to find it, or validation rules. The description doesn't mention parameters at all, leaving the agent completely in the dark about required input semantics.

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 'Delete proxy' is essentially a tautology that restates the tool name without adding meaningful context. While it clearly indicates a deletion action on a proxy resource, it doesn't specify what constitutes a 'proxy' in this system or differentiate this tool from sibling deletion tools like 'delete_profile' or 'delete_workspaces__wid__members__id_'.

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 absolutely no guidance about when to use this tool versus alternatives. There are multiple deletion tools in the sibling list (delete_profile, delete_workspaces__wid__members__id_, etc.) and no indication of which resource type this applies to, what prerequisites exist, or when this specific deletion operation is appropriate.

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