iyke_todo_complete

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

The description discloses the behavioral effect: it stamps completed_at. For a simple tool with no annotations, this adds necessary transparency, though it omits idempotency or error states.

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 sentence that is front-loaded with the primary action and provides an equivalent alternative; 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?

The description is adequate for a simple single-parameter tool but lacks details on return values, error conditions, or behavior on already-done todos.

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 sole parameter 'id' has no description in the schema (0% coverage), and the tool description provides no additional meaning or context about the parameter.

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 action 'Mark a todo as done' on the 'todo' resource, and distinguishes from sibling tools by explicitly noting equivalence to 'iyke_todo_update with status=done'.

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 explicitly states when to use this tool (to mark a todo as done) and provides an alternative (iyke_todo_update), making usage context very clear.

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