get_tpa_speed_adv_drag_k

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

With no annotations, the description carries the full burden. It discloses the requirement (USE_WING), the data type (UINT16), and the default value (1000). This provides useful behavioral context beyond a simple name repetition.

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: a single sentence with the name, explanation, requirement in parentheses, and type/default in brackets. Every part is essential, and the key info 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?

Given no annotations, no output schema, and no parameters, the description covers the essential aspects: what is retrieved, the prerequisite, and the value type/default. It lacks details on failure modes or return format, but such details are minimally necessary 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?

There are no parameters (0 params, schema coverage 100%), so no parameter descriptions are needed. The description adds value by stating the type and default of the value being retrieved, which is beyond what the empty schema provides.

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 verb 'Get' and the resource 'tpa_speed_adv_drag_k', specifying it as the aerodynamic drag coefficient for the advanced speed TPA physics model. Among many sibling getter tools, it distinguishes itself by naming the specific coefficient and model.

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 includes a prerequisite: 'Requires: USE_WING', indicating when this tool is applicable. However, it does not explicitly contrast with alternative tools or state when not to use it. The context is implied but not fully developed.

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