get_yaw_lowpass_hz

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

No annotations are provided, so the description must carry the full burden. It clearly describes that the operation retrieves a low-pass filter value, reducing yaw noise. It does not mention side effects or permissions, but as a 'get' operation, it is implicitly read-only and safe. The description adds value by explaining the filter's role and range.

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: one sentence explaining function, one usage tip, and a compact range/default notation. Every sentence adds value with no redundancy. It is front-loaded with the key purpose and well-structured.

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 simplicity of the tool (no parameters, no output schema), the description fully explains what the value represents, its effect, range, and default. It is complete for an agent to understand and invoke the tool correctly.

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 no parameters, and schema description coverage is 100% (trivially). The description adds meaning by explaining the parameter's role, range [0-500], default 100, and unit (Hz implicit in range). This compensates for the lack of param info in 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?

The description clearly states it retrieves the yaw_lowpass_hz value, which is a low-pass filter applied to the final yaw PID output. The verb 'Get' and the resource are unambiguous, and the context distinguishes it from other getter tools by specifying the exact parameter and its role.

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 does not explicitly guide when to use this getter versus alternatives. It includes a usage tip for the setter ('Set to 0 to disable...'), but for the getter itself, no situational guidance is provided. The purpose is clear from the name, but no sibling differentiation or context for selection is offered.

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