sync_todoist

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

No annotations, but description fully discloses reading env vars, not returning secrets, upserting, marking deleted, and that it does not write to Todoist. Comprehensive for a read sync.

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 purpose. Efficient but could be slightly tighter. Still well-structured.

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?

Covers main behavior but omits behavior for default db_path (null case). No output schema or annotation context, so a bit of gap exists.

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 only parameter db_path (optional, default null) is not mentioned in the description. With 0% schema coverage, the description fails to add any meaning beyond the schema, which is itself minimal.

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 it pulls Todoist board into local DB, read-only, and normalizes tasks. It distinguishes from siblings like import_todoist_obligations by syncing the full board.

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?

States when to use (sync Todoist board) and that it's read-only. Does not explicitly exclude alternatives or provide when-not-to-use guidance, but context is clear.

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