connect

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

Beyond the annotations, the description discloses that the tool replaces the current connection and that the switch takes effect immediately with no restart. This is useful behavioral context. The annotations already establish readOnlyHint=false and openWorldHint=true, so the description adds meaningful side-effect information without contradicting them.

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?

Three sentences, front-loaded with the tool's core purpose, followed by key details on the API key, replacement behavior, and immediacy. Every sentence earns its place and there is no filler.

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 single-parameter connection tool with no output schema, the description covers the purpose, the input needed, the side effect of replacing an existing connection, and the timing of the switch. An agent has enough information to invoke it correctly.

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%, so the schema already documents the apiKey parameter, including the tl_ prefix. The description adds where the key is created (TaskLite → Integrations → 'Connect Claude Code'), which is helpful, but it does not substantially change parameter semantics beyond what the schema provides.

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 states a specific verb and resource: connecting this machine to an existing TaskLite account, and additionally switching accounts. It clearly distinguishes itself from siblings like sign_up or disconnect by specifying 'existing account' and 'switch to a different one.'

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 gives clear context for when to use the tool: connect to an existing account or switch user/organization. It explicitly says 'use this to switch user or organization,' but it does not explicitly name alternatives such as sign_up or login or say when not to use those.

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