Agent Chef

Move the voting deadline

set_voting_deadline

Destructive

Override when the current ballot closes by setting an ISO timestamp or extending hours from the current deadline.

Instructions

One-off override of when the current ballot closes: an ISO timestamp, or extend_hours from the current deadline. Normally the deadline comes from the household schedule (vote_close_day/time); changing those via update_recipe_preferences re-syncs the current week.

Input Schema

TableJSON Schema

Name	Required	Description
`week_id`	No
`closes_at`	No	ISO 8601, e.g. 2026-09-09T18:00:00-07:00
`extend_hours`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`week`	Yes
`closes_local`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.1.1Oct 3, 2026

addedOutput schema / properties / week / properties / share_url

Added value: +{
+  "description": "Public page showing this week's winners",
+  "type": [
+    "string",
+    "null"
+  ]
+}

First observedv0.1.0Sep 7, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations provide destructiveHint=true, readOnlyHint=false, openWorldHint=false, so the safety profile is covered. The description adds meaningful behavioral context: this is a one-off override, and changing the schedule via update_recipe_preferences re-syncs the current week. With annotations covering the destructive/safety profile, a solid bonus is provided without contradicting them.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences front-load the action and then the normal behavior and alternative. Every clause carries information (override semantics, formats, sibling tool), with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be described. The description covers the one-off/mutation nature, both override mechanisms, and the persistent alternative. It is complete enough for this mutation tool, though it could note whether the override affects only the specified week_id.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 33%, so two of three parameters (week_id, extend_hours) lack schema descriptions. The description explains the format for closes_at (ISO timestamp) and clarifies extend_hours is relative to the current deadline, but does not document week_id. It adds partial compensation, so a mid-range score.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('override of when the current ballot closes') and specifies the two mutually exclusive mechanisms (ISO timestamp or extend_hours). The title 'Move the voting deadline' names the resource, and the description distinguishes the tool from schedule-based alternatives like update_recipe_preferences.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly frames this as a 'one-off override' versus the normal path ('Normally the deadline comes from the household schedule'), naming the sibling update_recipe_preferences as the persistent alternative. The agent knows when to use this tool and when to use the sibling instead.

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