mark_tasks_done

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

Discloses batch behavior, optional per-task notes, and reference formats. No annotations provided, so the description carries the full burden; it does a good job for a simple mutation tool.

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 concise sentences with no redundancy. The key information is front-loaded, and every sentence serves a purpose.

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 batch update tool without an output schema, the description covers purpose, usage, and parameters adequately. It could mention error handling (e.g., missing tasks), but overall sufficient.

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 input schema has 100% description coverage. The description adds value by explaining how to reference tasks (ID like '1' or '#1') and that notes are optional, enriching the schema's basic definitions.

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 marks multiple tasks as completed in a batch operation, with specific reference formats (ID or name). It differentiates from the singular sibling mark_task_done, making the tool's purpose unambiguous.

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?

Explicitly says it's efficient when several tasks are finished simultaneously, and mentions the singular alternative mark_task_done. Lacks explicit when-not-to-use scenarios, but the guidance is adequate.

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