set_tpa_speed_adv_mass

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

No annotations provided, so description carries full burden. It explains the parameter unit and default but fails to disclose behavioral traits such as persistence, immediacy of effect, or side effects. For a setter tool, such information is critical.

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?

Single sentence with additional details in brackets. Efficient but could be more structured (e.g., separate lines for unit, default, prerequisite). No wasted words.

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?

Covers parameter meaning and a prerequisite, but does not explain the broader context of TPA speed models or how this value interacts with other settings. For a simple parameter setter among many similar tools, additional guidance would improve completeness.

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?

Adds significant meaning beyond schema: explains that value is craft mass in g×0.1, specifies default (1000), and ties it to the advanced speed TPA model. Schema description merely says 'Value for tpa_speed_adv_mass (UINT16)' – description enriches it.

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?

Clearly states 'Set tpa_speed_adv_mass' and specifies it is craft mass (g×0.1) for the ADVANCED speed TPA physics model. Distinguishes from siblings like get_tpa_speed_adv_mass and other TPA-related tools by specifying the model variant.

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?

Mentions a prerequisite (Requires: USE_WING) but does not provide explicit guidance on when to use this tool versus other TPA settings or alternative models. With many sibling TPA tools, more context on selection criteria would improve clarity.

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