login

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

Discloses all important side effects: creates a personal API key named 'claude-code', stores it, uses password only once, and replaces the current connection. This is transparent about what the tool does beyond just authenticating.

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?

The description is concise and well-structured: first sentence states the action, second explains the side effect, third provides alternative usage. No redundant information.

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?

Provides all necessary context: what the tool does, its side effects, and when to use an alternative. Since there is no output schema, the description adequately covers the tool's behavior and usage context.

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 adequate descriptions for both email and password. The description does not add extra meaning beyond the schema, but the baseline is 3 given complete schema coverage.

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 specific action: connecting to an existing TaskLite account with email/password, or switching accounts. It also distinguishes itself from the sibling 'connect' tool by noting when to prefer it.

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 provides a usage condition: 'Prefer connect when the user already has a tl_ key.' It also explains the side effect of creating and storing an API key, giving clear guidance on how and when to use this tool.

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