Create a subsystem

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

With no annotations, the description must carry the full burden. It mentions file creation but does not disclose overwrite behavior, error handling, or prerequisites like project path. Basic disclosure is present but lacks depth.

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?

Two sentences: first explains action and outputs, second gives recommendation. No fluff, front-loaded, every sentence earns its place.

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 15 parameters and complexity, the description is brief. It does not explain how to use after creation or prerequisites like project existence. Adequate for selection but incomplete for full understanding.

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?

Schema description coverage is 60% (moderate). The description adds no parameter-level explanations, relying entirely on schema. Since it does not compensate for uncovered parameters, score is low.

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 action ('Scaffold a plain FTC subsystem class') and the resource (subsystem class, bench-test TeleOp, markdown doc). It distinguishes from siblings like create_opmode and create_teleop by specifying subsystem scaffolding.

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 provides context: 'This is the recommended way to structure robot code — one class per mechanism.' It implies when to use (for individual mechanisms) but does not explicitly state when not to use or list alternatives.

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