get_tpa_speed_basic_gravity

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

No annotations are provided, so the description must convey behavior. It clearly states that this is a read operation (Get), describes the value's purpose, and includes data type (UINT16) and default (50). There is no indication of destructive side effects, and the description is consistent with a simple getter.

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 the tool's purpose, followed by a note on requirements and the type/default. No unnecessary words; all information is front-loaded.

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 and no output schema, the description adequately explains the meaning and effect of the returned value. It also notes a prerequisite (USE_WING). It could mention range or typical values, but it is largely complete for its 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?

The input schema has no parameters (schema coverage 100%), so the description does not need to explain parameters. However, it adds value by explaining what the returned value represents (gravity factor affecting TPA response curve). This goes beyond the baseline of 3.

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 identifies the tool as retrieving a 'gravity factor for BASIC speed TPA' and explains its role in affecting the TPA response curve vs airspeed. This distinguishes it from related tools like get_tpa_speed_adv_drag_k or other get_tpa_* tools, which deal with different TPA parameters.

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 that the tool requires USE_WING, providing a prerequisite. However, it does not explicitly state when to use this tool versus alternatives (e.g., get_tpa_speed_basic_delay or set_tpa_speed_basic_gravity). Given the large number of sibling tools, more guidance would be helpful.

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