notlai_delete_tag

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

With no annotations provided, the description carries the full burden and discloses the critical behavioral trait that deleting a tag removes it from all notes. This is a significant side effect beyond a simple deletion, and it is clearly stated. No mention of authorization or reversibility, but adequate for a simple tool.

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 concise with two economically structured sentences. The first sentence states the purpose and side effect, and the second provides a usage hint. No extraneous content, front-loaded with critical information.

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 simple tool with one parameter and no output schema, the description covers the purpose, side effect, and how to obtain the input. It is fully complete for an agent to understand and invoke the tool correctly.

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 input schema description coverage is 100% and already includes the ULID format and sourcing hint. The tool description repeats this information but does not add additional meaning beyond what the schema provides, justifying a baseline score of 3.

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 clearly states the verb 'delete' and the resource 'tag by ID', and explains the important side effect of removing the tag from all notes. It distinguishes itself from sibling tools like notlai_create_tag and notlai_list_tags.

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 explicitly mentions 'Use notlai_list_tags to see available tags and their IDs', providing clear guidance on how to obtain the required parameter. It does not explicitly state when not to use the tool, but the context is clear for a deletion scenario.

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