nexo_plugin_remove

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

Description discloses one key behavioral trait (no file deletion), but without annotations, more details are needed about side effects, reversibility, prerequisites, or impact on other plugins. The disclosure is helpful but incomplete.

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?

Extremely concise single sentence (11 words) that front-loads the action and includes a clarifying disclaimer. Every word is necessary and contributes to understanding.

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 one-parameter tool, the description is largely complete. It explains the core function and a key limitation. However, it does not mention how to obtain the filename (e.g., via list) or describe the return value, which would be helpful.

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% with a clear description for the only parameter. The tool description adds no additional semantic value beyond what the schema already provides, so 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?

Description clearly states the action 'Unregister a plugin's tools from MCP' with a specific verb and resource, and explicitly distinguishes what it does not do ('does not delete files'), setting it apart from potentially similar operations like deletion.

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 explicit guidance on when to use this tool versus alternatives like nexo_plugin_list or nexo_plugin_load. The action is implied by the name but lacks contextual instructions.

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