connect_todoist

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

No annotations are provided, and the description only says 'Connect Todoist.' It does not disclose whether this initiates an OAuth flow, stores credentials, requires user interaction, or has side effects. The agent is left without any awareness of what will happen when invoking this tool.

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 extremely concise at two words, but it is under-specified for a connection tool. It earns its place as a clear subject-verb statement, but lacks critical context about the connection process. It is not verbose, but it is incomplete, so it does not merit a higher score.

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?

Given that there is no annotations, no output schema, and no parameters, the description is the only source of information. 'Connect Todoist' does not explain the connection flow, success/failure conditions, required authentication, or what happens after connection. This is completely inadequate for an agent to safely and correctly invoke the tool.

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 tool has zero parameters, so the schema is fully covered by virtue of being empty. The baseline for 0-parameter tools is 4, and the description does not need to explain parameters. No additional parameter semantics are required.

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 'Connect Todoist' uses a specific verb and resource, making it clear that this tool establishes a connection to Todoist. It distinguishes from siblings like disconnect_todoist and connect_m365_account by naming the target service. However, it does not elaborate on what 'connect' entails, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus alternatives such as disconnect_todoist or other connection tools. No context is provided about prerequisites, when a user would need to connect Todoist, or how it relates to the many Todoist task management tools in the sibling list.

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