terminal_get_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read operation, but the description does not explicitly state whether the tool is read-only, whether it makes any state changes, or what happens for invalid terminal IDs. There is no mention of side effects or internal behavior.

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 extremely concise with no fluff. It clearly states the core action. However, it is so brief that it misses key context; still, for a simple single-parameter read tool, brevity can be considered appropriate.

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 no output schema and no annotations, the description should explain what 'detailed information' includes and how it differs from terminal_list. It does not mention return format, possible errors, or behavior. The tool is simple enough that a slightly richer description would have been sufficient, but it currently lacks completeness.

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 100%, so the parameter terminal_id is already well-documented with its source and purpose. The description adds no additional parameter meaning, but the schema covers it adequately; hence baseline 3 applies.

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?

Description states a clear verb-resource pair: 'Get terminal detailed information'. However, it does not differentiate from sibling tools like terminal_list, which likely also returns terminal information, so there is a slight ambiguity about which tool returns overview vs details.

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 main description gives no guidance on when to use this tool versus alternatives. The parameter schema hints that terminal_id comes from terminal_create or terminal_list and that this gets details for a specific session, but this is not stated in the tool description itself. There is no explicit mention of exclusions or when to prefer sibling tools.

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