get_blackbox_disable_rpm

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

No annotations are provided, so the description must bear the full burden. It notes the prerequisite (USE_DSHOT_TELEMETRY) and mentions the type (UINT32) and default (OFF), but does not disclose whether the operation is read-only, has side effects, or what the response format looks like. For a getter, read-only behavior is implied but not stated.

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 very concise—one sentence plus a requirement note and type/default. It is front-loaded with the key purpose. The formatting (colon, underscores) is slightly messy but does not significantly hinder readability.

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 absence of an output schema, the description should explain what the tool returns. It does not explicitly say 'returns the current value of the setting'. The prerequisite and type are helpful, but the lack of return value information leaves the agent guessing about the response structure.

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 input schema has zero parameters, and schema coverage is 100%. The description adds value by specifying the type (UINT32) and default (OFF), which are not present in the schema. This exceeds the baseline expectation for a no-parameter tool.

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 'Exclude RPM telemetry data' which aligns with the tool name. It identifies the resource (blackbox_disable_rpm setting) and the action (get). However, it does not explicitly state that it returns the current value of this setting, leaving ambiguity for new users.

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 on when to use this tool versus the many sibling tools (e.g., get_blackbox_disable_gyro, get_blackbox_disable_acc). The description does not mention when-not-to-use or provide context for choosing among alternatives.

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