mcp_delete_option

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

With no annotations provided, the description must fully disclose behavioral traits. It only states the action but does not mention irreversibility, side effects, authorization requirements, or what happens when the option does not exist. This lack of context leaves the agent without critical safety information.

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 (one short sentence) and to the point. It is not verbose, but it could be slightly more informative without sacrificing brevity. However, for a simple tool, this level of conciseness is acceptable.

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 simplicity of the tool (single required parameter, no output schema, no nested objects), the description is minimally complete. It covers the basic purpose but lacks details on return values or side effects. More context would help the agent use it safely.

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 input schema describes the parameter 'key' as 'Option name', which is clear. Since schema coverage is 100%, the description does not add extra meaning but is adequate. No additional parameter details are needed beyond what the schema provides.

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 an option' clearly states the action and resource. It is specific enough to indicate that this tool removes an option, though it does not elaborate on what constitutes an 'option' in this context (e.g., WordPress options). The verb is unambiguous and the resource is identifiable from the tool name and parameter.

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 no guidance on when to use this tool versus alternatives. Among siblings, there are tools like mcp_get_option, mcp_set_option, and mcp_bulk_get_options, but no mention that this tool is for deleting a single option, nor are there any conditions or prerequisites for its use.

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