get_motor_pwm_rate

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

Discloses data type (UINT16), valid range (200-32000), and default value (480), giving the agent clear expectations. No annotations provided, so description carries full burden; it handles it well.

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?

Two concise sentences: first identifies the value, second adds relevance and constraints. No wasted words, front-loaded with the key purpose.

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?

Covers the meaning, range, default, and applicability (brushed motor mode only). Could mention recommended usage scenarios, but for a simple getter this is adequate.

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?

Input schema has 0 parameters with 100% schema description coverage. Description adds no parameter info, but none is needed. Baseline 4 is appropriate as it adds value about the returned value's constraints.

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?

Description clearly states it gets the PWM frequency for brushed motor mode, explicitly noting irrelevance for DSHOT protocols, distinguishing it from related siblings like get_motor_pwm_protocol.

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 'Not relevant for DSHOT protocols' provides a clear exclusion criteria. However, it does not explicitly state when to use this tool or name alternative tools, but the context is sufficient.

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