schedule_command

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

The description discloses the delayed execution behavior, but lacks details such as whether the command runs once or repeatedly, if it can be canceled, or any side effects on the item. With no annotations, more transparency would be beneficial.

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 with an example, containing no redundant words. It efficiently conveys the core functionality.

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 there are three required parameters and no output schema, the description is insufficient. It does not clarify what itemName refers to (the item to target? a name for the schedule?) or the expected format of command. The example is illustrative but not precise.

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 coverage is only 33% (only delayMs is described), but the description does not explain itemName or command parameters beyond the example. The example 'turn off in 20 minutes' implies parameter use but is vague about the exact string format.

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 'Schedule a command' and specifies the timing 'after a delay', with an illustrative example. It distinguishes from siblings like 'send_command' (immediate) and 'automation' (more complex scheduling).

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 clearly indicates the tool is for delayed command execution, but does not explicitly state when not to use it or mention alternative tools like 'send_command' for immediate execution.

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