forget_file

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

Without annotations, the description carries the burden of disclosing behavior. It states that it '删除所有记忆' (deletes all memories) for the file, which conveys destructiveness and scope. However, it doesn't mention irreversibility, permissions, or side effects on other components (e.g., embeddings), leaving some behavioral gaps.

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, front-loaded sentence stating the core action, followed by a list of trigger phrases that aid usage. It is efficient, though the trigger list is somewhat lengthy.

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?

The tool is simple (one parameter, no output schema), but without annotations, the description should cover more context. It confirms the destructive action and usage triggers, but doesn't mention error cases, irreversibility, or interaction with sibling tools, making it adequate but not comprehensive.

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 the file_path parameter already has a clear description ('要删除记忆的文件的完整路径'). The tool description adds little beyond '指定文件', so it doesn't provide additional semantic value beyond the schema.

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 uses a specific verb '删除' (delete) and resource '指定文件的所有记忆' (all memories of the specified file), clearly stating the tool's function. It distinguishes from sibling tools (embed_file, search_memory, list_memories) by targeting removal of memories rather than creation, search, or listing.

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?

It provides explicit trigger phrases ('忘记这个文件', '删除记忆', etc.) indicating when to use the tool. It doesn't explicitly contrast with alternative tools but offers concrete user-intent examples, giving clear usage context.

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