connect_todoist

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

With no annotations, the description carries the full burden. It only says 'Connect' without disclosing side effects, whether the token is stored, validated, or if an existing connection is replaced. The truncation leaves critical behavioral aspects unexplained.

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 a truncated sentence fragment, making it structurally incomplete. While short, it fails to deliver a complete thought, which is a significant issue for agent comprehension.

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?

Despite the tool's simplicity (no parameters, no output schema), the description is incomplete. It doesn't explain the connection flow, what happens on success/failure, or how this relates to sibling Todoist tools, leaving a substantial gap.

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?

The schema has zero parameters, so the baseline is 4. The description adds value by mentioning the personal API token and its source (Todoist settings), which is the key input for the operation. However, it doesn't clarify how the token is provided to the tool (e.g., prompt, environment variable), preventing a higher score.

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 connects to Todoist using a personal API token, with a specific verb and resource. It distinguishes from siblings like disconnect_todoist and todoist_* operations, though the truncated sentence doesn't fully explain what 'connect' entails.

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?

No guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, such as needing to connect before using todoist_* tools, or conditions for reconnecting. The description only gives a token retrieval path but omits usage context.

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