get_session_diagnostics

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

No annotations are present, so the description must fully disclose behavioral traits. It only says 'comprehensive diagnostics' without specifying what is checked (e.g., connectivity, latency, config), or whether the operation is read-only or has side effects. This vagueness forces reliance on the tool name.

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 concise (one sentence) but oversimplified. It prioritizes brevity over necessary detail; a slightly longer description with added context would improve usability without sacrificing clarity.

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 tool has three parameters (one required), no parameter descriptions, and several sibling tools offering similar diagnostics, the description is insufficient. It does not explain the output or scope of 'comprehensive diagnostics', making it hard for an agent to choose appropriately.

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 0%, meaning the param definitions lack any textual explanations. The description does not mention any parameter details (host, port, username) or their roles, leaving the agent without guidance on what values to provide or how they affect the diagnostics.

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 uses 'Get comprehensive diagnostics for an SSH session', which clearly indicates the verb (Get) and resource (diagnostics for an SSH session). However, it does not distinguish this tool from sibling tools like get_connection_health_report or get_performance_metrics, which may also provide diagnostic information.

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. There is no mention of prerequisites, context, or exclusion criteria, leaving the agent to guess based on the name alone.

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