mgmt_delegate_delete

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

No annotations are provided, so the description carries the full burden. It only says 'Remove delegate' without disclosing effects, reversibility, required permissions, or any consequences of the operation.

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 very concise, but it is essentially a URL and a short phrase. It lacks structure or front-loading of useful information. While it is not verbose, it is under-specified and does not provide a meaningful sentence.

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 deletion tool, the description fails to explain the operational context—such as what happens when a delegate is removed, whether it is reversible, or any prerequisites. With no output schema and no annotations, the description should have been more comprehensive.

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 provides descriptions for both parameters (user_login and pretty), achieving 100% coverage. The description adds no parameter-specific information, but the schema already covers this, so a baseline 3 is appropriate.

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 states 'Remove delegate' which clearly identifies the action (remove) and resource (delegate). It differentiates from siblings like mgmt_delegate_create and mgmt_delegates_list. However, it is extremely terse and lacks any additional context.

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 versus alternatives. It does not mention any prerequisites, conditions, or scenarios where removing a delegate is appropriate.

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