browser_untag_tab

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

No annotations are provided, so the description carries the full behavioral burden and does not meet it. It does not say whether removal is reversible, whether the tag disappears from all tabs or just one, what happens if the tag name does not exist, or what is returned. Only the bare fact of mutation is conveyed.

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?

It is short, but this is under-specification rather than conciseness — three words that leave scope, target, and parameter meaning unresolved. There is no wasted text, but there is far too little of it for a mutation tool.

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?

With no annotations, no output schema, an undocumented required parameter, and a dense sibling set (browser_tag_tab, browser_resolve_tag, browser_list_tags), the definition is nowhere near complete enough for an agent to invoke it 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?

One parameter ('name') at 0% schema description coverage, and the description adds no meaning: is this the tag label, a tag id, or a tab identifier? The only hint is that a tag is being removed, which leaves the required 'name' argument ambiguous.

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?

States a verb and resource ('remove' + 'tag'), so the basic action is identifiable. However, it never clarifies the target: the tool name says 'untag_tab', implying a tag is detached from a specific tab, but the description could equally read as deleting a tag globally, which is what browser_list_tags / browser_resolve_tag territory suggests. It does not distinguish itself from browser_tag_tab.

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?

No when-to-use, prerequisites, or alternative is given. The agent is not told when to untag versus deleting/replacing a tag via browser_tag_tab, nor whether the tag must already exist. Only the most generic inference ('use this to remove a tag') is available.

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