get_tpa_curve_stall_throttle

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

No annotations exist, so the description carries full burden. It states the return type (UINT8) and default (30), implying it is a read query. It does not explicitly confirm safety or side effects, but the 'get_' prefix and parameter-less schema strongly suggest no destructive behavior.

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 a single sentence that packs the action, resource, meaning, prerequisite, type, and default value. No redundant words; every token adds value.

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 (0 params, no output schema, no annotations), the description covers the core purpose, application domain, prerequisite, and data format. It could hint at read-only behavior, but that is implicit. Overall, it provides sufficient context for correct invocation.

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?

There are zero parameters, and the schema coverage is 100% (empty object). Per guidelines, baseline for 0 parameters is 4. The description adds no parameter info because none is needed.

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 action ('Get'), the resource ('tpa_curve_stall_throttle'), and explains the meaning ('Throttle % below which the craft is considered stalled for wing/fixed-wing TPA'). It fully distinguishes this from the many other get_ siblings.

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 specifies the prerequisite constant 'USE_ADVANCED_TPA' and the context ('for wing/fixed-wing TPA'), giving clear guidance on when to use. It does not explicitly mention when not to use or offer alternatives, but the context provided is sufficient for an agent.

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