migrate_monitor_session

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

With no annotations, the description must fully disclose behavioral traits. It mentions updating messages and merging/renaming sessions, but does not clarify whether the operation is destructive (e.g., old session deleted), if there are side effects on related data, or if authorization is needed. Critical details about what happens to the old session after migration are omitted.

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 efficient sentences: first states the action and effect, second lists use cases. No redundant words, front-loaded with main purpose. Every sentence adds value.

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 data migration operation with no output schema, the description should cover return value, error conditions, and full lifecycle effects. It adequately states purpose and use cases but lacks details on what is returned (e.g., success status, count of migrated messages) and error scenarios (e.g., missing session IDs).

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% with both parameters described ('Original session ID to migrate from', 'Target session ID to migrate to'). The description adds a brief restatement but no additional meaning, constraints, or examples. Baseline score of 3 is appropriate given the schema already defines parameters clearly.

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 tool migrates messages from old to new session ID, merging/renaming sessions. It mentions use cases (session continuity, combining splits, correcting identifiers). However, it does not explicitly differentiate from the sibling tool 'migrate_shared_session' which likely has a similar role for shared sessions, leaving ambiguity about scope.

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 some guidance on when to use it (session continuity, combining split sessions, correcting identifiers) but lacks explicit when-not-to-use conditions, alternatives, or prerequisites (e.g., session existence, permission requirements).

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