disconnect_todoist

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

With no annotations, the description carries the behavioral burden and does add useful specificity: it says the API token stored on this computer is removed. However, it does not disclose irreversibility, whether a reconnect is required afterward, whether remote Todoist data is affected, or what happens if no token is present.

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 single, front-loaded sentence with no redundant clauses. It states the action and the specific resource affected without unnecessary preamble.

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 simple zero-parameter disconnect tool, the description provides enough context to invoke it correctly and understand the main local effect. A minor gap remains around post-disconnect state or error behavior, but the core operation is complete.

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?

This tool has zero parameters, so there are no parameter semantics to explain. The baseline for a parameterless tool applies, and no description gap exists in this dimension.

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 uses a specific verb and resource: 'Disconnects Todoist', and it clarifies the concrete effect by stating that it removes the API token stored on this computer. This is clearly distinguishable from connect_todoist and from unrelated todoist_* task operations.

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 intended use is implied by the verb and effect, but the description does not explicitly state when to choose this over alternatives, whether it should be used only when connected, or what prerequisites exist. It is adequate but lacks explicit routing guidance in a large sibling set containing connect_todoist and many other disconnect_* tools.

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