admin_get_connection_session

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

With no annotations provided, the description must fully disclose behavioral traits. While 'Get' indicates a read operation, it does not explain what the returned status includes, error behavior, or any prerequisites like admin rights. The term 'reconnection session' adds some context but lacks detail on side effects or response format.

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 concise sentence that fronts the action and resource, with no redundant or extraneous information. Every word contributes to 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?

For a simple one-parameter read tool, the description is adequate but not complete. It lacks details about the expected response structure or possible status values, which would be helpful given there is no output schema. It also does not clarify whether the tool is limited to admin contexts, despite the admin_ prefix.

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 already provides a description for sessionId ('Connection session UUID'), and coverage is 100%. The description adds 'reconnection' to the context, implying the sessionId could be from either a connection or reconnection session, which slightly expands the parameter's scope beyond the schema description.

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 specifies the action 'Get' and the resource 'connection or reconnection session status' with the method 'by session ID.' It clearly differentiates from sibling tools like admin_create_reconnection_session and admin_cancel_connection_session, which handle creation and cancellation.

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 when you have a session ID and need its status, but it does not explicitly state when this tool should be preferred over alternatives such as check_connection_status or admin_cancel_connection_session. No 'when not to use' or alternative guidance is provided.

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