set_api_token

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

No annotations are provided, so the description carries full burden. It discloses that the token persists only for the current session, a key behavioral trait. However, it omits details on error cases or side effects.

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 (4 sentences) with no redundant information. It front-loads the purpose and benefit, then adds necessary behavioral and parameter details efficiently.

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 configuration tool with one parameter and an existing output schema, the description covers all needed aspects: purpose, usage context, parameter source, and session persistence. It 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?

The schema only defines 'token' as a string with no description. The description adds critical value by specifying where to obtain the token ('get from https://...'), making the parameter's meaning and usage clear.

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 action ('Set or update the Todoist API Token at runtime') and the resource ('API Token'), distinguishing it from all sibling tools which deal with tasks, projects, and other entities.

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 explains the benefit ('switch accounts without restarting') and implies use when needing to change accounts dynamically, but does not explicitly state when not to use or compare with alternatives (there are none).

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