get_tpa_curve_pid_thr0

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

No annotations provided, so the description carries the burden. It discloses the unit (×0.1%), default value (200 = 20%), and a required feature flag (USE_ADVANCED_TPA). This adds behavioral context beyond a simple 'get'.

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?

Two short sentences front-loaded with purpose, then unit, default, requirement, and type. Every part earns its place with no fluff.

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 getter with no parameters, the description provides essential context (unit, default, requirement). It lacks info about the return format but is sufficient for a single-value read.

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 0 parameters, so no parameter documentation needed. Baseline for 0 params is 4, and the description adds relevant output context without needing to explain parameters.

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 gets the PID value at zero throttle for the TPA curve, with a specific verb and resource. It distinguishes from siblings like get_tpa_curve_pid_thr100 by noting 'at zero throttle'.

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 mentions a requirement (USE_ADVANCED_TPA) but does not explicitly state when to use this tool versus alternatives like the setter or other getters. Implicit usage is clear but no explicit guidance.

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