magg_remove_server

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. While 'Remove a server' implies a destructive action, it fails to mention any side effects, such as permanent deletion, disconnection, or cleanup of associated resources. The output schema exists but is not referenced, leaving the agent unaware of what response to expect.

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 extremely concise at just four words, with no wasted text. It is front-loaded with the verb. However, it may be overly terse, missing important context that could be added without significant bloat.

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 the tool performs a destructive removal operation with only one parameter and no annotations, the description is insufficient. It does not explain return values (despite an output schema existing), confirm requirements, or outline post-removal effects. The description leaves the agent underinformed for correct and safe usage.

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% because the single parameter 'name' is described as 'Server name to remove'. The tool description adds no additional semantic information beyond what the input schema already provides, so a baseline score of 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 clearly states the verb 'Remove' and the resource 'server', making its primary action immediately obvious. It effectively distinguishes from sibling tools like magg_add_server, magg_disable_server, and magg_enable_server, which perform different actions.

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 offers no guidance on when to use this tool versus alternatives. It does not specify prerequisites, such as whether the server should be disabled before removal, or context in which removal is appropriate. This lack of usage direction may lead to incorrect invocation.

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