Mark a Boardroom todo done

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

Without annotations, the description provides good behavioral details: sets status, stamps completed_at, posts event, and notes agent_id required. This covers the mutation and side effects adequately.

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?

Three sentences front-load the purpose with no wasted words. Efficient and clear.

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 no output schema or annotations, the description covers the effect and required input adequately. Slight gap: what agent_id refers to is not explained, but the tool name and context make it reasonable.

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% and the description only mentions agent_id is required without explaining what the parameters represent or any format constraints. For a 2-param tool, this adds minimal value.

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: 'marking a todo as done' with specific details on what it does (set status, stamp timestamp, post event). It distinguishes itself from sibling tools like create_todo, update_todo, delete_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 it's a 'shortcut' but does not explicitly explain when to use this vs. alternatives like update_todo. No guidance on when-not or prerequisites beyond agent_id requirement.

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