set_tpa_low_rate

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

No annotations provided. The description mentions it's an INT8 with default 20 and its effect, but fails to disclose whether setting requires reboot, is persistent, or what happens on out-of-range values. The schema's min/max are unrealistically large, and the description does not clarify the actual permissible 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: two sentences plus a technical note in brackets. Every word adds value, front-loading the action and effect.

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 simple single-parameter setter without output schema, the description covers the purpose and effect adequately. Missing details like persistence or range enforcement are minor given the tool's simplicity.

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?

Schema coverage is 100%, but the description adds value by noting the type 'INT8' and default '20', which are not in the schema. This helps the agent know typical values, though the schema's range is misleading.

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 sets 'tpa_low_rate' for D-term attenuation at minimum throttle to reduce shaking. It specifies the verb 'Set' and resource, but does not differentiate from similar TPA-related siblings like set_tpa_rate or set_tpa_breakpoint.

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 implies use when 'reducing D-term shaking during throttle chops' but provides no explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned despite many TPA-related siblings.

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