RemoveTag

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds real value beyond that by clarifying what is NOT destroyed: the tag definition and its associations to other items survive, which is the key question an agent has about a removal operation.

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 short sentences with zero filler; the action and its scope come first, and the preservation guarantee follows immediately.

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, idempotent two-parameter unlink operation with full schema coverage, complete annotations and an output schema, the description supplies everything an agent needs. Only an explicit pointer to the contrasting sibling (DeleteTag) is missing.

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%; both parameters carry examples and even discovery hints ('Use ListTags to find it', 'Use ListItems or SearchLibrary to find it'). The description adds no parameter-level meaning, so the baseline 3 applies.

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?

Specific verb (Remove) plus resource (tag) with explicit scope limiting the operation to 'one item'. The clause 'The tag itself and its other items are kept' implicitly separates it from Matter_DeleteTag, though it never names a sibling explicitly.

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 phrase 'from one item' implies the correct use case (unlinking a tag from a single item rather than deleting or bulk-removing), but there is no explicit when-to-use, when-not-to-use, or named alternative such as Matter_DeleteTag or Matter_AddTag.

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