read_tmux_pane

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

No annotations are provided, so the description must fully disclose behavior. It correctly states that reading only occurs on explicit invocation and implies a read-only operation. However, it lacks details on potential side effects, performance implications, or error conditions, making it adequate but not thorough.

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 three sentences, each adding value: action, use case, and invocation guarantee. It is front-loaded with the primary function and contains no redundant or filler content.

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?

The description covers purpose and usage context well, but with no output schema or annotations, it should clarify the return format (e.g., plain text) and potential errors. The current description is adequate for a simple read tool but lacks completeness.

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 100%, so the schema already documents all parameters. The tool description adds no extra semantic meaning beyond the schema, such as usage tips or interdependencies. Thus, it meets the baseline but does not exceed it.

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 'Reads the content of a tmux pane' with a specific verb and resource. It further explains the use case for interactive sessions, and the sibling tool list_tmux_sessions has a distinct purpose (listing sessions, not reading content), so there is no ambiguity.

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 explicit context for when to use (interactive sessions like git rebase, vim, conflict resolution) and states no background monitoring. However, it does not explicitly mention when not to use or alternative tools besides the sibling, though the sibling is not a direct alternative.

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