stop

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

With no annotations provided, the description carries full burden. It mentions 'terminate script execution immediately', which hints at destructive behavior, but lacks details on permissions needed, irreversible effects, error conditions, or what happens to session data. For a potentially destructive tool, this is insufficient.

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, front-loaded sentence with zero wasted words. Every element ('stop', 'debug session', 'terminate script execution immediately') contributes directly to understanding the tool's core function.

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 no annotations, no output schema, and a potentially destructive operation, the description is minimally adequate. It covers the basic action but lacks critical context like side effects, return values, or error handling. The 100% schema coverage helps, but overall completeness is limited.

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 100% description coverage for its single parameter ('session_id'), so the baseline is 3. The description doesn't add parameter details beyond the schema, but since there's only one parameter and the tool's purpose is straightforward, this is adequate for a slightly above-baseline score.

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 ('stop') and the target ('debug session'), with the verb 'terminate' providing specific behavioral context. It distinguishes from siblings like 'close_session' by emphasizing immediate termination of script execution, not just session closure.

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 context ('debug session') but doesn't explicitly state when to use this tool versus alternatives like 'close_session' or 'detach'. It provides no guidance on prerequisites, exclusions, or comparison with sibling tools.

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