pane_set_label

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

Beyond the idempotentHint=true annotation, the description discloses a side effect: the label also affects which `app` filters match in get_logs/diagnose. This adds behavioral context without contradicting annotations.

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 sentences, front-loaded with the primary action, no redundant words. Every part 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?

Given the simple setter nature, the description covers core usage, side effects, and context, which is sufficient. No output schema needed, and annotations fill in safety/retry behavior.

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% with descriptions, and the tool description adds extra context: 'from pane_list' for id, and 'e.g. the project name' for label, enhancing understanding beyond the schema alone.

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?

Description clearly states 'Set a pane's display label', giving a specific verb and resource. It also notes an additional effect on app filtering, which distinguishes it from sibling pane tools like pane_list or pane_close.

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 mentions '(Cockpit only)', implying a context restriction, but does not provide explicit when-to-use or when-not-to-use guidance, nor alternatives. The extra effect on filtering is noted but not framed as a usage condition.

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