resetSession

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

Describes key behaviors: rebuilds session, releases prior locks, re-logs in. No annotations provided, so description carries full burden; it covers the main behavioral traits but doesn't detail auth or rate limits, which is acceptable for a recovery tool.

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 concise sentences, front-loaded with action and purpose. Every sentence adds value with 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?

For a simple tool with one optional parameter and no output schema, the description is largely complete. It explains purpose, usage, and behavior. Missing explicit mention of return value or error handling, but sufficient for effective use.

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?

Only one optional parameter 'connection' with schema description covering 100%. Description adds no additional meaning beyond the schema; baseline 3 is appropriate.

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?

Clearly states it recovers a broken write session by rebuilding a fresh stateful ADT session and re-logging in. Distinguishes from sibling tools like logout, login, dropSession by specifying its specific recovery role.

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?

Explicitly tells when to use (lock/edit fails with 'stale lock' or 'stateful lost') and when NOT to use (logout), explaining consequences: logout permanently disables client, resetSession restores and releases locks.

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