edb_set_tty

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

Describes redirection of stdin/stdout/stderr, adding behavioral detail beyond annotations (idempotent, destructive, openWorld). Annotations already give hints, description confirms effect.

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?

Well-structured with clear Args/Returns sections, minimal sentences, no fluff. Front-loaded with purpose.

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 one-parameter tool, covers all needed info: what it does, parameter, return type. Output schema exists but description adds value.

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?

Includes Args section detailing the 'params' object and 'tty_path' with example ('/dev/pts/0'), adding meaning beyond schema (which only has title and description).

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?

Clearly states 'Set the terminal device for the debugged program's I/O.' Specific verb and resource, distinct from siblings which focus on breakpoints, memory, etc.

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?

Mentions equivalence to EDB's TTY configuration, implying usage context. No explicit when-to-use or alternatives, but no conflicting tools exist among siblings.

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