terminal.info

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

No annotations are provided, so the description carries full disclosure burden. 'Get terminal session information' suggests a read-only operation, but it does not explicitly state behavioral traits like being non-destructive or requiring specific permissions. The description is adequate but lacks explicit safety guarantees.

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 sentence with no wasted words, fitting within the scope of the tool's function. Every word contributes to clarity.

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?

Given the single parameter and no output schema, the description is minimal but sufficient for a simple info retrieval tool. However, it could be slightly improved by hinting at the type of information returned (e.g., session state, metadata). Users of sibling tools may expect more detail.

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 coverage is 100%, and the parameter 'sessionId' already has a description ('Session ID from terminal.start — use exact value'). The tool description adds no further semantic information beyond what the schema provides.

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 'Get terminal session information' clearly states the action (get) and resource (terminal session information), effectively distinguishing it from sibling tools that perform actions like type, press, or kill.

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 implies usage for retrieving session data but provides no explicit guidance on when to use this tool versus alternatives like terminal.target_info or terminal.list. No exclusions or contexts are mentioned.

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