register_session

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

With no annotations, the description discloses auto-detection from git, leadership auto-claim, idempotency, and capture for channel events. Covers key behavioral aspects.

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?

Description is moderately concise with each sentence adding value. Could be slightly shorter but front-loads main purpose and auto-detection details.

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?

Tool has one required parameter that is not documented, leaving a significant gap. Otherwise, behavioral context is thorough. Output schema existence is noted but not referenced.

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?

Single required parameter 'objective' has 0% schema description coverage and is not mentioned in the description. The agent has no guidance on what to provide for 'objective'.

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?

Description clearly states the tool registers a Claude session and starts heartbeating, with specific details on auto-detection and idempotency. It distinguishes from siblings like heartbeat and deregister.

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?

Provides context on when to use (for registration) and behavior (auto-detection, leadership claim, idempotency). Does not explicitly contrast with alternatives but implies this is the initial setup step.

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