pty-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions termination of remote PTY, which implies a destructive action, but doesn't clarify if this is reversible, requires specific permissions, or has other consequences like data loss. More details on behavior would improve transparency.

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, efficient sentence that front-loads the main action and includes an additional detail about remote PTY termination. There is no wasted text, making it highly concise and well-structured for quick understanding.

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 complexity of a destructive operation with no annotations and no output schema, the description is incomplete. It lacks information on success/failure outcomes, error handling, or how this tool interacts with siblings like 'detach_session'. More context is needed for safe and effective use.

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?

The schema has 0% description coverage, so the description must compensate. It doesn't add any meaning to the 'session_id' parameter beyond what's implied by the tool name. However, with only one parameter, the baseline is higher, but the description fails to explain what a session ID is or where to obtain it, leaving a gap.

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 action ('close') and resource ('session'), and specifies that it also terminates a remote PTY, which adds useful detail. However, it doesn't explicitly differentiate from sibling tools like 'detach_session', which might have similar functionality but different behavior.

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?

No guidance is provided on when to use this tool versus alternatives like 'detach_session' or when it's appropriate to close a session. The description lacks context about prerequisites, such as whether the session must be active or owned by the user, or any side effects beyond termination.

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