delete_context

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

No annotations are provided, so the description carries the full burden. 'Delete' implies destructive behavior, but the description doesn't disclose irreversibility, permanence, whether the operation can be undone, or any side effects. The only behavioral hint is that the parent entity survives. For a destructive mutation tool with zero annotation coverage, more transparency is needed.

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 compact two-sentence fragment that conveys its core purpose efficiently without wasted words. It's appropriately short for a simple single-parameter tool, though it could include slightly more detail without becoming verbose.

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 destructive mutation tool with zero annotations, zero schema coverage, and no parameter documentation, the description is notably thin. While an output schema exists (which helps the agent understand return values), the description fails to address the critical 'ref' parameter semantics or the permanence of deletion. Given the destructive nature and lack of structured support, this should provide more guidance.

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 description coverage is 0%, and the description mentions nothing about the 'ref' parameter - what it references, what format it takes, or how to obtain valid refs. The description names the resource (subtopic) but never connects that to the required 'ref' parameter. The schema only says it's a string, leaving the agent to guess what identifier to supply.

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 states 'Delete a single subtopic' which is a specific verb (delete) plus resource (subtopic). It additionally clarifies the parent entity is preserved, which adds useful scope nuance. However, it doesn't explicitly differentiate from sibling tools like delete_entity or upsert_context, though the term 'subtopic' provides some distinction.

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 phrase 'Parent entity is preserved' gives some implied usage context, suggesting this is safe for removing sub-elements without affecting parent structures. However, there's no explicit when-to-use vs when-not-to-use guidance, nor any mention of alternatives like delete_entity or upsert_context for removal scenarios.

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