template_delete

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While '删除' (delete) implies a destructive operation, the description doesn't specify whether this deletion is permanent, requires specific permissions, has confirmation prompts, affects dependent resources, or provides any success/failure response format. For a destructive operation with zero annotation coverage, this is inadequate.

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 appropriately concise with two lines: a purpose statement and parameter documentation. It's front-loaded with the main purpose and wastes no words, though the formatting with extra whitespace could be slightly cleaner.

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 operation with no annotations and no output schema, the description is incomplete. It doesn't address critical behavioral aspects like permanence, permissions, error conditions, or response format. While the parameter semantics are covered, the overall context for safe and correct tool invocation is insufficient.

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 description explicitly lists the parameter 'name: 模板名称' (name: template name), which provides clear semantic meaning for the single required parameter. With 0% schema description coverage and only one parameter, this description adequately compensates by explaining what the parameter represents, though it doesn't provide format examples or constraints.

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 index template), which provides a clear verb ('delete') and resource ('index template'). However, it doesn't differentiate from sibling tools like 'index_delete' or 'template_get', making it vague about what specifically distinguishes this template deletion operation from other deletion operations in the system.

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 no guidance on when to use this tool versus alternatives. There are multiple deletion-related sibling tools (doc_delete, index_delete, alias_delete, etc.), but the description offers no context about when template deletion is appropriate versus other deletion operations or prerequisites for using this tool.

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