delete_widgetDelete a widget by ID.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Widget ID to delete (from list_widgets). |
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Confirmation that the widget was deleted from its page. | |
| success | Yes | True when the call succeeded. A failure comes back as an error result instead. |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -nullNew value: +{
+ "$schema": "http://json-schema.org/draft-07/schema#",
+ "additionalProperties": false,
+ "properties": {
+ "data": {
+ "description": "Confirmation that the widget was deleted from its page."
+ },
+ "success": {
+ "description": "True when the call succeeded. A failure comes back as an error result instead.",
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "success"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true and readOnlyHint=false, so the description does not need to repeat that deletion is destructive. It adds minimal behavioral context (e.g., that the ID comes from list_widgets), but does not disclose side effects, reversibility, or permissions beyond what annotations imply. This is acceptable given annotation coverage, but no extra value is added.
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 a single, front-loaded sentence with zero wasted words. It immediately states the action and target, making it efficient for an agent to parse.
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 single-delete operation, the description, combined with annotations and the input schema, provides enough information for an agent to invoke it correctly. It does not mention return values, but an output schema is present (indicated by context signals). The lack of explicit guidance on side effects is covered by destructiveHint, so nothing critical is missing.
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 fully documents the single parameter 'id' with a clear description, so schema_description_coverage is 100%. The tool description does not add any additional meaning about the parameter beyond what the schema already provides, so the baseline 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 'Delete a widget by ID' clearly states the action (delete), the resource (widget), and the identifying attribute (ID). It distinguishes itself from sibling delete_widgets (plural) and delete_page, so an agent can immediately recognize this is for a single widget 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?
The description does not explicitly mention when to use this tool versus alternatives like delete_widgets (bulk deletion). It implies single-deletion via the singular 'a widget' and the ID parameter, but does not name any alternatives or conditions. This leaves the decision to the agent based on context rather than explicit guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.