ksp_flight_stage

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

With no annotations, the description carries the full behavioral burden, and it discloses almost nothing: it does not say the action consumes/advances a stage, whether it is reversible, what happens when no stages remain, or that it requires an active flight scene. 'Activate' implies a mutating, one-way operation but that is inference, not disclosure.

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?

A single front-loaded sentence with zero waste. It is arguably too terse for the amount of undisclosed behavior, but as a matter of structure and economy it is clean.

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 zero-parameter action with no output schema and no annotations, the minimum viable content is present, but the irreversible/one-shot nature of staging and the flight-scene prerequisite are both absent. An agent can call it, but not confidently predict or recover from the result.

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 tool takes zero parameters, so per the baseline there is nothing for the description to clarify. A 4 is the appropriate ceiling given the schema is empty and needs no compensation.

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?

States a specific verb ('Activate') and a specific resource ('the next KSP staging step'), so the agent knows exactly what the call does. It does not, however, distinguish itself from adjacent siblings such as ksp_flight_activate_part or ksp_editor_set_stage, which is the gap that keeps it off a 5.

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?

There is no when-to-use guidance, no statement of prerequisites (e.g. must be in the flight scene), and no reference to alternatives like ksp_flight_activate_part or the editor-side staging tools. The flight-prefixed name is the only signal that this is the in-flight staging action.

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