ksp_flight_maneuver_nodes

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

No annotations are provided, so the description carries the burden, but it does signal a non-mutating read ('Read ... maneuver nodes'). It adds useful disclosure about what data is surfaced (delta-v, burn vector, timing, next-patch orbit), yet omits whether this requires an active flight scene, what happens with zero nodes, or the response shape.

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 filler; the verb and resource lead and the payload details follow compactly.

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 read tool with no output schema, the description does the minimum-plus by enumerating the returned fields (delta-v, burn vector, timing, next-patch orbit). It would be stronger with a note about scene prerequisites or behavior when no nodes exist, but nothing critical is missing.

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 no parameters, so the baseline is 4; the schema has no properties to misinterpret. The description correctly implies no inputs are needed to read the current node set.

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 (Read) and a precise resource (native KSP patched-conic maneuver nodes), and enumerates the data returned: node-coordinate delta-v, burn vector, timing, next-patch orbit. It does not, however, explicitly distinguish itself from siblings like ksp_flight_add_maneuver_node or ksp_flight_clear_maneuver_nodes, which operate on the same maneuver-node concept.

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 preconditions (e.g. must be in flight scene), and no routing to alternatives such as ksp_flight_transfer_plan or ksp_flight_add_maneuver_node. The agent must infer usage entirely from the read semantics and the name.

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