session_set_claude_id

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 does explain the binding action and the adoption context, but it doesn't disclose whether the operation overwrites an existing binding, validates the session ID, or what happens on conflict. For a mutation-like operation, this leaves some ambiguity.

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 crisp sentences deliver the purpose, usage condition, and exclusion. Every word earns its place, with no redundancy or fluff.

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 two string parameters and no output schema, the description covers the core functionality and required conditions. It misses potential details like error behavior or whether the ID must already exist, but given the simplicity, the description is reasonably complete.

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 0% and the description provides the only semantic clue. It does indicate that `name` is the target name and `claude_session_id` is the existing ID to bind, which gives basic meaning. However, it doesn't mention constraints like uniqueness or format of the name/ID, so it only partially compensates for the lack of schema descriptions.

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 a specific verb 'Bind' and clearly identifies the resource ('an existing Claude conversation ID') and the target ('to *name* for future `--resume`'). It distinguishes this from sibling session tools by explaining it's only for adopting sessions not created by the server, which is a unique purpose.

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 states when to use ('Only needed to adopt a session this server did not create') and when not to use ('new sessions are assigned an ID automatically'). This gives clear guidance on the preconditions and distinguishes it from the normal session creation flow.

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