pane_send_text

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent operation. The description adds the useful behavioral nuance that text is sent without an Enter keystroke, but it does not explain what 'raw text' means at the pane level, whether it is inserted at the cursor, or what happens on failure.

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 a single front-loaded sentence with no wasted words. It communicates the action and the key constraint immediately.

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 two-parameter tool with an output schema and annotations, the description covers the core action and the no-Enter behavior. However, it omits pane_id semantics and does not explicitly route the agent away from similar tools such as pane_run or pane_send_keys.

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 carry the burden for both parameters. It clarifies that 'text' is raw text sent to the pane, but it provides no meaning for 'pane_id' beyond the parameter name, leaving an important identifier undocumented.

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 states a specific verb ('Send') and resource ('raw text to a pane'), and adds the key qualifier 'without pressing Enter' that distinguishes it from a command-submission tool. However, it does not explicitly name sibling tools like pane_run or pane_send_keys, so sibling differentiation is only implicit.

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 phrase 'without pressing Enter' implies when this tool is appropriate versus a tool that submits commands, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent can infer the context but must consult sibling tools to be certain.

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