get_tpa_low_rate

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

No annotations are provided, so the description carries the burden for behavioral disclosure. It correctly implies a read-only operation (via 'Get') and includes the data type and default value ([INT8, default: 20]). The description is clear and does not contradict any annotations.

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 plus a bracketed technical detail. Every word serves a purpose, and it is front-loaded with the purpose.

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 no output schema, the description covers the essential purpose and effect. It could briefly mention the range of the return value, but the INT8 type implies a common range. Overall sufficient for a simple getter.

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 zero parameters, so the baseline is 4. The description goes beyond by annotating the returned value's type and default (INT8, default: 20), which adds valuable context for the agent.

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 gets the tpa_low_rate, defines it as 'D attenuation at minimum throttle (TPA Low)', and explains its effect ('Reduces D-term shaking during throttle chops.'). This distinguishes it from other TPA-related tools like get_tpa_rate or get_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 this tool is used to read the TPA low setting, but does not explicitly state when to use it versus alternatives. There is no mention of when not to use it or comparisons to sibling get_tpa_* tools.

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