set_blackbox_disable_rpm

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

With no annotations provided, the description must carry the full behavioral transparency burden. It states the action (disable RPM telemetry) but does not explain what this means for logging, persistence, or side effects. The required build flag is mentioned but not elaborated.

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 brief (one sentence plus parenthetical requirement) and front-loads the key action. However, the mention of 'UINT32' contradicts the schema's string type, reducing clarity slightly.

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's simplicity (one parameter, no output schema) and the schema's enum, the description covers the basic use case. However, it lacks broader context about blackbox logging or when this setting is relevant (e.g., for RPM filtering). Additional detail would improve completeness.

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 schema covers 100% of parameters with enum and description, so baseline is 3. The description adds the default value 'OFF' and notes the type 'UINT32', though the schema uses a string enum. This adds minimal value beyond the schema.

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 action 'Set' and the resource 'blackbox_disable_rpm', and explains its function 'Exclude RPM telemetry data'. However, it does not explicitly distinguish itself from sibling tools like set_blackbox_disable_gyro, relying on the name and brief explanation.

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 notes a prerequisite ('Requires: USE_DSHOT_TELEMETRY'), providing conditional context. No guidance on when to use this tool vs alternatives (e.g., other blackbox disable settings) is given, and no when-not-to-use scenarios are mentioned.

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