Set Playdate accelerometer values

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description adds the useful context that this sets simulator accelerometer axes rather than real-device state. However, it does not disclose side effects such as event generation, clamping, units, or coordinate system, so behavioral transparency beyond annotations is limited.

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 sentence that is front-loaded with the action and target. There is no filler, redundancy, or unnecessary detail; every word earns its place.

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?

For a simple setter with an output schema and safety annotations, the description covers the core resource and fields, and the schema documents the pid parameter. It is not fully complete because units and value ranges for x, y, and z are missing, and there is no guidance on when this tool is appropriate, leaving an agent to infer or guess valid accelerometer semantics.

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 only 25%, and the description does not fill the gap. It merely restates that x, y, and z are accelerometer values without specifying units, valid ranges, or axis orientation; the optional pid is already documented in the schema, so the description adds little semantic value beyond the property names.

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 names a specific action ('Set'), a specific resource ('Simulator accelerometer'), and the exact fields (x, y, z). It is clear and implicitly separates this from sibling tools such as playdate_set_crank and playdate_set_button by focusing on accelerometer axes, though it does not explicitly name an alternative.

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?

No guidance is given on when to use this tool vs. alternatives, no prerequisites, and no exclusions. The only contextual hint is the word 'Simulator', which weakly implies this is for simulation rather than physical hardware, but there is no explicit when-to-use guidance.

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