iyke_todo_update

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

No annotations are provided, so the description must disclose all behavioral traits. It only says 'Only supplied fields are changed' (implying partial update) but omits any side effects, error handling, validation constraints, or consequences of the update. This is insufficient for safe usage.

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 sentences with no filler. The first sentence defines the core action, the second provides a usage tip and sibling alternative. Every sentence earns its place; it is appropriately sized and front-loaded.

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?

With 6 parameters (including enums) and no output schema, the description should cover return values, error scenarios, and parameter relationships. It only hints at merge behavior ('only supplied fields are changed') but lacks details on what the response looks like, how IDs are validated, or any preconditions. Incomplete for a tool of this complexity.

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?

Schema description coverage is 0%, meaning the description provides no individual parameter documentation. It only mentions the 'status' parameter by example ('Pass status="done"') but does not clarify semantics of body, title, assignee, blocker_id, or the meaning of each status enum value. This adds negligible value beyond the schema.

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 tool performs a 'Partial update of a todo' with the verb 'update' and resource 'todo'. It distinguishes from siblings by mentioning iyke_todo_complete as an alternative for setting status to '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?

Explicitly states 'Only supplied fields are changed', guiding usage. Also provides a specific recommendation: 'Pass status="done" or use iyke_todo_complete for the common case', which clarifies when to use this tool versus a sibling.

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