Delete a Captured Thought

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

Discloses that deletion is 'destructive and irreversible — no undo, no trash'. Since no annotations provided, description fully addresses behavioral traits.

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 purpose, no wasted words. Structured effectively.

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 tool with 1 param, no annotations, no output schema, the description covers all essential aspects: purpose, irreversibility, proper usage, and alternative actions.

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% and schema already explains the 'id' parameter well. Description adds no additional meaning for the parameter itself, staying at baseline.

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 'permanently delete a specific captured thought by its ID' with specific verb and resource. Distinguishes from siblings by emphasizing destructive nature.

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?

Explicitly states when to use (user asks to delete/remove/forget) and when not (proactively, as side effect, on guess). Provides alternative: use search_thoughts/list_thoughts first and confirm with user.

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