stop_session

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

The description only states 'stop and clean up' without details on side effects, resource release, or whether it is destructive. With no annotations, the description fails to disclose behavioral traits beyond the basic action.

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. It is front-loaded and to the point.

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 tool with one parameter and no output schema, the description is too minimal. It lacks context about when to stop, prerequisites, expected effects, and how it relates to sibling tools. An agent would need more information to use it correctly.

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% with a description for session_id. The tool description adds no extra meaning; it neither clarifies format nor provides usage context beyond the schema. Baseline score for high coverage is appropriate.

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 'Stop and clean up a PTY session.' clearly states the specific verb-action (stop and clean up) and the resource (PTY session). It distinguishes from siblings like start_session or list_sessions by indicating termination and cleanup.

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 send_keys or run_command. It lacks context such as prerequisites or indications for stopping a session.

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