stty

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

Description discloses default read-only behavior and conditional destructive change via allow_change, adding context beyond destructiveHint annotation. Does not detail what settings are supported for modification, but effectively explains safety profile.

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?

Three sentences, front-loaded with main purpose, no wasted words. Efficiently conveys all essential information.

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?

With 5 parameters fully described in schema and no output schema, description provides necessary context about behavior and use cases. Could mention output format more precisely, but enough for agent selection.

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?

Adds meaning beyond schema by listing example settings (baud rate, line discipline, control characters) and explaining roles of allow_change and dry_run. Schema coverage is 100%, so baseline 3; description surpasses 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?

Clearly states 'Inspect or modify terminal device settings', specifying verb and resource. Distinguishes from sibling 'tty' by noting that tool is for settings inspection, not simple TTY detection.

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?

Explicitly says 'Use to query terminal state before operations that depend on it' and 'Not for simple TTY detection — use 'tty''. Provides clear when-to-use and when-not-to-use with alternative.

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