unregister_tool

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

No annotations are provided, so the description carries the full burden. The description clearly states a destructive removal action, but it does not disclose side effects, reversibility, or any prerequisites. For a simple removal this is adequate but lacks depth.

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 very short and gets to the point. The second sentence provides the actual meaning. The first line '注销工具' is slightly redundant with the tool name but acts as a heading. No unnecessary words.

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 (1 parameter, no nested objects) and the presence of an output schema, the description sufficiently covers the core action. It does not address error cases or expected output, but for a basic unregister operation this is acceptable.

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 100% (only param tool_name is described). The description adds little beyond the schema, just referring to '指定的工具' (the specified tool). It does not elaborate on what valid tool_names are or where to find them.

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 explicitly states the tool removes a specified tool from the tool registry. The verb '移除' (remove) and resource '工具注册表' (tool registry) are clear and distinguish it from siblings like register_tool.

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?

Usage is implied: use this when you need to remove a tool from the registry. However, there is no explicit mention of when not to use it or alternatives (e.g., if you only need to view definitions, use get_tool_definition). No exclusions are stated.

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