send_text

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

The description only reveals the submit behavior (appending Enter) but omits other behavioral traits like effects on session state, handling of edge cases (e.g., empty text, inactive session), or required prerequisites, despite no annotations existing to cover these.

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 provide the core functionality and an important option without extraneous information. The structure is front-loaded and efficient.

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 3 parameters and no output schema, the description is minimally adequate. It covers the main action and the submit toggle but lacks details about session_id sourcing, return value, or error conditions.

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?

With 0% schema description coverage, the description adds meaning only for the 'submit' parameter (explaining its effect). It does not elaborate on 'text' or 'session_id' beyond their names, leaving some ambiguity for the agent.

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 the tool's action ('Type text into a session') and its key option ('Set submit=true to append Enter'), differentiating it from sibling tools like send_key which handles key presses.

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 lacks guidance on when to use this tool versus alternatives such as send_key or start_session. No context for appropriate or inappropriate scenarios is provided.

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