start_program

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

Annotations provide no useful behavioral hints (all false), so the description carries the full burden. It only says 'Start' and does not disclose whether the call blocks, returns immediately, interrupts the current program, or what happens if the named program is not found.

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 a single, focused sentence with no filler. It front-loads the action and resource without repeating the tool name or schema details.

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 one-parameter tool, the description is minimally adequate: it states what is started and that it must already exist on the NXT. But with no annotations, no output schema, and no mention of execution behavior or alternatives, it leaves important context for an agent to infer.

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 schema has 0% description coverage and only declares a string parameter named 'name'. The description's mention of a stored '.rxe program' weakly implies that 'name' should be the stored program name, but it does not clarify file extension formatting, name matching rules, or how to discover valid names.

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 states a specific action ('Start') and resource (an '.rxe program already stored on the NXT'), making the tool's purpose clear. It doesn't explicitly contrast with siblings like run_behavior, but the '.rxe' qualifier provides enough distinction from behavior-focused tools.

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 phrase 'already stored on the NXT' implies a prerequisite and a clear use case: launching an existing program file. However, it does not explicitly mention alternatives, such as run_behavior for behaviors or stop_program for stopping, so some inference is required.

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