Set Playdate crank state

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

Annotations already indicate this is a mutating, idempotent, non-destructive operation. The description adds the meaningful detail that the crank supports both angle and docked states, but it does not disclose additional side effects or runtime requirements. This is adequate but not rich.

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?

A single, front-loaded sentence captures both modes with no redundancy. It is efficient and avoids unnecessary detail.

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, combined with the schema's anyOf branches and the presence of an output schema, gives an agent enough to invoke the tool correctly. A slightly more explicit statement about mutual exclusivity of degrees and docked would make it fully complete, though the schema already enforces this.

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 description gives plain-language meaning to the schema's otherwise bare parameters: 'degrees' is the crank angle in degrees and 'docked' represents the docked state. This helps an agent interpret the anyOf branches correctly beyond what the schema types alone convey.

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 states a specific verb ('Set'), the resource ('crank'), and the two supported modes ('position in degrees' or 'docked'). It is immediately clear what the tool does and how it differs from the sibling tools, which target other Playdate controls.

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 makes the tool's purpose obvious, but it does not explicitly explain when to choose this tool over alternatives or when not to use it. Since no sibling tool targets the crank, this is a minor gap rather than a critical one.

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