delete_note_tag

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

Discloses the critical behavioral constraint that system tags are protected/deletion-resistant. Since no annotations exist, description carries full burden; could improve by stating error behavior (exception vs silent failure) or idempotency (safe to retry?).

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?

Single sentence, ~20 characters. Action verb front-loaded, constraint cleanly parenthesized. Zero redundancy or waste while capturing essential scope limitation.

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?

Adequate for a 2-parameter deletion tool with no output schema. Covers primary function and important constraint. Minor gap: could specify return behavior (void/success boolean) or confirmation of deletion.

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 has 100% description coverage ('笔记 ID', '要删除的标签 ID'), clearly documenting both note_id and tag_id. Description does not repeat these details but doesn't need to; baseline 3 appropriate when schema already fully documents parameters.

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?

Excellent specificity: '删除' (delete) + '笔记的指定标签' (note's specified tag) clearly identifies the resource and action. The parenthetical constraint '(系统标签不可删除)' immediately distinguishes scope/capabilities from sibling tools like delete_note or remove_note_from_topic.

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?

Provides explicit when-not guidance '(系统标签不可删除)' indicating system tags are protected. However, lacks explicit when-to-use guidance versus siblings like remove_note_from_topic or the inverse operation add_note_tags.

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