update_prompt_version

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

Annotations indicate mutation (readOnlyHint=false) but no destruction. The description adds that the tool only affects label assignment and clarifies null behavior ('null clears the label'). This adds meaningful context beyond the basic annotation flags.

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 concise sentences. The first states the core purpose, the second elaborates on null behavior and prerequisite workflow. No unnecessary words; all content earns its place.

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 three required parameters and an output schema, the description covers the essential: what it does, how null works, and where to get label IDs. No gaps for this complexity level.

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 coverage is 100%, providing baseline 3. The description adds value by explaining the label_id parameter's role in assigning/removing labels and guiding the agent to use 'list_prompt_labels' for ID lookup. This goes beyond schema descriptions.

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 it updates a prompt version's label assignment, with specific verbs ('assigns', 'removes', 'clears'). It distinguishes itself from siblings like 'update_prompt' (which updates the prompt itself) and 'list_prompt_labels' (for looking up label IDs).

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 provides clear usage context: it only assigns or removes a label, and recommends looking up IDs with 'list_prompt_labels'. It does not explicitly state when not to use it or list alternative tools, but the scope is well-defined.

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