todoist_project_archive

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

No annotations provided; description only states archiving hides and can be restored. Does not disclose permissions, effect on tasks, or default archive behavior (true). Burdens agent with incomplete information.

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?

Two sentences, no wasted words. Front-loaded with verb and resource. Concise and efficient.

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?

Tool is simple with well-documented schema. Lacks some behavioral details like permissions or task effects, but adequate for basic understanding given no output schema and low complexity.

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?

All three parameters have descriptions in input schema (100% coverage). Description adds no extra meaning beyond what schema provides. Baseline 3 is appropriate.

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?

Description clearly states the verb 'Archive or unarchive' and the resource 'project in Todoist', with effect 'hidden from main view but can be restored'. Distinguishes from siblings like todoist_section_archive and todoist_project_delete.

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 explicit guidance on when to use vs alternatives like todoist_project_delete or todoist_archived_projects_get. Purpose implies usage for hiding projects without deletion, but lacks when-not or comparison.

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