complete_todo

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

The description adds behavioral context beyond annotations by mentioning that Huly may trim future work slots and run issue automation. This is useful beyond the destructiveHint=true annotation, though it could elaborate on the return value or additional side effects.

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 two concise sentences, front-loading the purpose and adding relevant behavioral context without unnecessary detail.

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?

Given the complexity of the locator parameter and the presence of an output schema, the description provides sufficient high-level context. It could be slightly more comprehensive about return values or confirmation, but it is adequate.

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 description adds meaning beyond the input schema by advising to prefer issue/title/owner forms when the raw ToDo ID is unknown, and by clarifying that omitting 'doneOn' uses the current time. This enhances the schema's metadata.

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 'Complete' and the resource 'Planner ToDo', specifying the mechanism 'by setting doneOn'. This distinguishes it from sibling tools like 'reopen_todo' and 'update_todo'.

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 for completing a ToDo but does not explicitly state when to use this tool versus alternatives like 'reopen_todo' or 'update_todo'. No direct guidance on when not to use it.

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