mark_all_todos_done

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

The description states a state change (mark as done) but adds no additional behavioral traits beyond the obvious. With 'openWorldHint': true in annotations, more context about side effects or reversibility would be helpful.

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 redundancy or fluff. Every word adds value.

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 no-parameter tool, the description is adequate but could be more complete by clarifying scope (e.g., across all projects) or noting that it only affects the current user.

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 no parameters; schema coverage is 100% trivially. Baseline for 0 params is 4, and the description adds no parameter info because none exist.

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 verb 'mark', the resource 'all pending GitLab to-do items', and the scope 'for the current user'. It distinguishes from the sibling 'mark_todo_done' which presumably marks a single item.

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 implies usage when one wants to clear all pending todos, but lacks explicit when-to-use or when-not-to-use guidance, especially given the sibling 'mark_todo_done' exists for single items.

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