Delete a log streaming configuration to stop sending configuration or network logs to the configured destination. Choose the log type to remove the stream.
Delete a log streaming configuration. Logs will stop being sent to the configured destination.
| Name | Required | Description | Default |
|---|---|---|---|
| logType | Yes | The log type to stop streaming: 'configuration' or 'network' |
Changes observed during successful MCP inspections.
v0.13.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate destructiveness and idempotency. The description adds the specific effect ('Logs will stop being sent'), which provides some additional context but does not disclose further behavioral traits like reversibility.
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?
Two concise sentences, front-loaded with the action and immediate consequence. No unnecessary words.
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 delete operation with one parameter and no output schema, the description is complete: it states what is deleted and the outcome. No missing context.
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 single parameter 'logType' is fully described in the schema with enum and description. The tool description adds no additional parameter information, but schema coverage is 100%, so 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?
Description clearly states the action ('Delete') and resource ('log streaming configuration'), and distinguishes from siblings like set_log_stream_config and get_log_stream_config. The effect is also described.
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 clear context for when to use the tool (to stop log streaming), but does not explicitly mention when not to use it or provide alternatives. Implied by the action.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.