calibrate_magnetometer

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

The description explains the user action required (rotate flight controller through all orientations when prompted) and warns about MSP/CLI session ordering. However, it does not disclose side effects (e.g., overwriting previous calibration, internal state changes), and no annotations exist to fill this gap. Some additional behavioral context would be helpful.

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 extremely concise: two sentences. The first sentence states the purpose, and the second provides critical usage notes. Every word earns its place with no redundancy or filler.

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 the tool has no parameters and no output schema, the description is largely sufficient. It covers the action and the crucial sequencing requirement. However, it omits any mention of return values (success/failure) or duration, which an agent might need to gauge next steps. Still, for a simple calibration with no params, it is reasonably complete.

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 tool has zero parameters, and schema coverage is 100% (empty schema). Per calibration, baseline is 4 for 0 parameters. No further parameter information is needed.

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 tool calibrates the magnetometer (compass), a specific resource. The verb 'calibrate' is action-oriented. Although sibling 'calibrate_accelerometer' exists, the resource type (magnetometer vs. accelerometer) naturally distinguishes them.

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 explicitly advises calling this tool before any CLI tools in the same session, noting that MSP cannot be used after CLI mode. This provides important sequencing context. It does not, however, mention when not to use it or alternatives, but the guidance is clear for the intended workflow.

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