complete_task

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

Description adds details beyond annotations: sets status=COMPLETED, populates completedBy/completedAt, preserves in history unlike delete_task. This enriches the agent's understanding.

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 focused sentences, no fluff. Front-loaded with key action and alternatives. Every word earns its place.

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?

Lacks return value or confirmation details (no output schema). Agent knows what the tool does but not what to expect back (e.g., updated task object vs success status). Adequate for a simple mutation but could be more 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?

With 0% schema description coverage, the description should clarify the 'id' parameter meaning. It only implies it's a task ID, but doesn't confirm it's required or provide constraints. Agent may need to infer from context.

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 ('mark as done/completed') and the resource ('task'). Distinguishes from delete_task and update_task by explaining behavioral differences.

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?

Gives explicit usage triggers ('mark done', 'complete', 'finish') and notes it's a discoverable alternative to update_task. Does not explicitly state when not to use, but clear enough for most cases.

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