remote_session_end

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 does not mention that ending a session is irreversible, what happens to associated processes, or any permission requirements, leaving the agent with only the verb 'End' as a cue.

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?

Two short sentences, front-loaded with the primary verb, and no redundant words.

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 one-parameter tool with high schema coverage, the description covers the core functionality and the special 'all' case. It doesn't describe return values or side effects, but given the simplicity, it is reasonably complete; however, a safety warning would improve it.

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 input schema already fully describes the sessionId parameter including 'all' and omit behavior (100% coverage). The description's 'Use sessionId='all'' adds no new information, so 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?

The description clearly states the verb 'End' and the resource 'remote session(s)', making the tool's function explicit. It also distinguishes from sibling start/status tools by implying termination, and the 'all' variant is highlighted.

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 provides a specific usage instruction: 'Use sessionId='all' to end all sessions', which tells the agent how to target all sessions vs a specific one. However, it doesn't mention alternatives or when not to use, but given the tool's unique role, this is sufficient clear context.

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