td_destroy_operator

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

With no annotations, description discloses critical behavioral traits: confirmation requirement (safety guard) and restrictions (cannot delete root/bridge). Adds value beyond schema by explaining these constraints.

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 in Chinese, no filler. Front-loaded with action and essential constraints. Every word earns its place.

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?

Adequately covers main action and constraints, but lacks details on side effects (e.g., disconnections), prerequisites, or return behavior. Could be more complete for a destructive tool.

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 0% so description must explain parameters. It clarifies confirm must be true, but provides no detail for 'path' parameter. Only partial compensation for missing schema descriptions.

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?

Description clearly states the tool deletes an Operator, with Chinese verb '删除' and resource 'Operator'. It distinguishes from sibling tools like td_create_operator and td_list_operators by focusing on destruction.

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?

Specifies must pass confirm=true and constraints (cannot delete root or bridge itself), but lacks explicit guidance on when to use vs. alternatives like td_disconnect_input or td_save_project. Usage context is implied rather than explicit.

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