zen_tag_tab

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

With no annotations provided, the description fully carries the behavioral disclosure burden. It explicitly states that tags live in memory and do not survive bridge restarts unless re-tagged, a critical behavioral trait. This is valuable for an agent to understand persistence, though it does not cover potential side effects like overwriting existing tags.

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 exceptionally concise: two sentences. The first sentence states the primary purpose, and the second adds a critical behavioral note. No wasted words, perfectly front-loaded.

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 tagging tool with no output schema, the description covers the core purpose, persistence behavior, and the companion tool. It does not explain error conditions (e.g., invalid tab_id) or whether tagging is additive, but these are minor gaps. Overall, it sufficiently informs an agent for basic use.

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 0%, so the description must compensate. It adds minimal meaning: `name` is described as 'memorable' and `tab_id` is implied to be a tab identifier, but no details on format, constraints, or valid values are provided. This is insufficient for full parameter understanding.

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 tool's verb ('Give a tab a memorable name') and resource (tab). It also references the complementary tool `zen_resolve_tag` for later use, providing a usage context. However, it does not explicitly differentiate from sibling tools like `zen_untag_tab` or `zen_list_tags`, which slightly reduces clarity.

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 implies the use case (tag for later reference via `zen_resolve_tag`), but does not explicitly state when to use or avoid this tool, nor mention alternatives. The guidance is implied rather than direct, meeting the minimum bar.

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