tmux_id

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

No annotations are provided, so the description carries the full burden. It accurately describes the tool as printing an ID—a simple read operation with no side effects. The behavior is transparent for the simplicity of the tool, though no additional context (e.g., permissions, edge cases) is given.

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 two short sentences, front-loading the core action. Every sentence adds value: the first states what it does, the second gives a use case. No wasted words.

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 tool has no parameters, no output schema, and a trivial action, the description is complete. It explains the tool's purpose and provides a typical use case. Nothing essential 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?

The input schema has no parameters and schema description coverage is 100% (empty). With zero parameters, the description need not add parameter info. The baseline score of 4 is appropriate as the description adds no param details, but none are needed.

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 it prints the tmux ID of the current pane, using a specific verb ('Print') and resource ('tmux ID'). It distinguishes from sibling tools like tmux_name (which likely prints the name) by specifying the output is the ID from $TMUX_PANE.

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?

Description mentions 'useful for self-identification when labeling', giving implied context. However, it does not explicitly state when to use this over alternatives (e.g., tmux_name for session name, tmux_resolve for resolving IDs), nor does it provide exclusion criteria. Usage is implied but not fully guided.

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