get_dshot_edt

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

Discloses that it provides additional ESC data, that FORCE enables EDT even when bidirectional mode is off. No annotations exist, so description carries the burden. Missing info on side effects or permissions, but for a read operation this is acceptable.

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?

Description is brief but packs essential info: purpose, feature, requirements, and type/default. A bit cluttered but efficient for a parameterless getter.

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?

For a tool with no parameters and no output schema, the description adequately explains what it returns (additional ESC data) and special behavior (FORCE). Requirements are stated. Sufficient among many sibling getters.

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 zero parameters, yet description includes '[UINT8, default: OFF]' which suggests a parameter that doesn't exist. This is misleading and contradicts the schema. No parameters to document, so baseline is 4, but the extraneous info lowers the score.

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 retrieves extended DSHOT telemetry (beyond RPM). Distinguishes from other get_dshot_* tools like get_dshot_bidir by specifying it provides additional ESC data.

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?

Implies usage for obtaining extended telemetry and notes force mode. Mentions required compile flags (USE_DSHOT, USE_DSHOT_TELEMETRY) but lacks explicit when-to-use vs alternatives or when-not-to-use.

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