get_motor_idle

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

With no annotations provided, the description carries the burden. It explains that the tool retrieves a value sent to ESCs when armed, implying a read-only operation. However, it does not explicitly state that it is safe or has no side effects, nor does it mention any required permissions or rate limits.

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, using a single sentence plus a bracketed specification. Every element serves a purpose: name, purpose, role, and technical constraints. No wasted words.

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 there is no output schema, the description effectively communicates what the tool returns and its context. It includes the value's role, units note, and constraints. It could be slightly more explicit about it being a read-only operation, but overall it is sufficient for understanding.

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 no parameters, so the schema imposes no burden. The description adds significant value by explaining what the returned value represents (idle throttle), its units caveat, and its range and default. This helps an agent understand the semantics of the output beyond just the name.

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 retrieves the idle throttle value sent to ESCs when armed, specifying it is the minimum non-zero motor command. It also provides the data type, range, and default. This distinguishes it from the sibling 'set_motor_idle' tool.

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 implicitly indicates when to use this tool (to read the idle throttle value), but does not explicitly state when not to use it or provide alternatives. Given there are no other readers for this specific value, the context is clear enough for an agent.

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