forget_context

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

With no annotations, the description carries the full burden of disclosing behavior. It explicitly says 'Delete', indicating a destructive action, and specifies the scope ('one saved context item'). It also clarifies that the id is a context id, adding helpful context. It could mention irreversibility or permission requirements, but the core destructive behavior is clearly conveyed.

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, well-structured sentence. It front-loads the key action ('Delete') and is concise without any wasted words. Every phrase contributes value.

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 the tool's simplicity (one parameter, output schema present), the description covers the essential aspects: what it does, what it operates on, and where the id comes from. It doesn't detail return values (covered by output schema) or error handling, but for a basic delete tool, it is sufficiently complete.

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 only defines item_id as an integer with no description. The tool description adds meaning by explaining that the id is a saved context item id, and specifically from list_context/search_context. This gives the agent crucial semantic understanding of the parameter that the schema itself lacks.

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 clearly states the action: 'Delete one saved context item by its id', specifying both the verb (delete) and the resource (saved context item). It also distinguishes itself from siblings by indicating the id origin (from list_context/search_context), making it unambiguous.

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 on how to obtain the id ('from list_context/search_context'), implying the workflow of first listing/searching then deleting. It doesn't explicitly state when not to use it or alternatives, but the sibling tool names make the delete-vs-create/retrieve distinction obvious.

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