get_yaw_motors_reversed

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

No annotations provided. Description explains the setting's effect ('reverse yaw PID output sign') and includes data type [INT8, default: OFF]. However, it does not confirm idempotency or that it is a read-only operation (though 'get' implies it).

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?

Very concise: one sentence with action, one with usage, and a type hint. Front-loaded with the key purpose. No superfluous text.

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 parameterless getter with no output schema, the description covers purpose, usage, and data type. Lacks explicit mention of return value, but it's implied. Sufficient for decision-making.

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?

No parameters exist, so schema coverage is 100%. The description adds value by annotating the data type and default value, which are absent from the input 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?

Description specifies verb 'Get', resource 'yaw_motors_reversed', and explains it reads the reverse yaw PID output sign setting. It distinguishes from sibling 'set_yaw_motors_reversed' by name and usage context.

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?

States 'Use when motor spin direction is swapped from normal', providing a clear scenario. Does not explicitly list when not to use or alternatives, but the sibling setter is implied.

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