reset_thinking_profileClears all recorded thinking-profile events and restores the default profile by resetting thinking-profile.yaml, removing stored preference signals.
Clear all thinking_profile_events and reset thinking-profile.yaml to defaults.
This erases all recorded preference signals and restores the default profile.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses destructive behavior ('erases all recorded preference signals') but could be more explicit about irreversibility or side effects. No annotations exist to shift the burden.
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 sentences, front-loaded with action, no fluff. Every word is necessary and informative.
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 no parameters and no annotations, the description covers the essential effects. Could mention whether the action is reversible or if any confirmation is needed.
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?
No parameters (0 params, baseline 4). The description adds context about what resources are affected (events and yaml), compensating for the absence of parameter info.
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?
Clearly states the action ('clear all thinking_profile_events and reset thinking-profile.yaml to defaults') and resource, distinguishing it from siblings like 'update_thinking_profile' or 'record_thinking_event'.
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?
Implies usage for resetting to defaults but lacks explicit guidance on when to use vs. alternatives (e.g., 'update_thinking_profile') or any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.