admin_create_reconnection_session

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

No annotations are provided, so the description carries the full burden. It mentions the creation side effect and return values, but does not disclose permission requirements, any invalidation of previous sessions, or reversibility. For a mutation tool, this is a notable gap.

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?

One concise sentence that front-loads the main action, then gives the key return values. No wasted 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?

The tool has a single parameter and no output schema; the description names both output fields (reconnectionSessionId and reconnectionLink) and the required condition. It is complete for a simple tool, though additional info on admin authorization 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?

Schema coverage is 100% for the single parameter, so the description is not required to add parameter details. The description's mention of the prerequisite account status aligns with the schema's 'UUID of the account to reconnect' but does not add extra semantics.

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 ('Create a reconnection session') and the target resource ('account with status reconnection_required'). It distinguishes from sibling tools like admin_get_connection_session by emphasizing creation and the prerequisite status.

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 an implicit usage condition ('for an account with status reconnection_required') but does not explicitly discuss alternatives or when not to use. Since it lacks references to sibling tools like admin_get_connection_session or admin_connect_account, it only implies usage context.

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