List FTC sample OpModes

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

No annotations provided, so description carries full burden. The description implies a read-only listing operation with no side effects. It doesn't detail pagination or ordering, but a listing tool is straightforward enough. The description adds context that the samples are official and reference implementations.

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, no wasted words. The first sentence states the action and scope, the second adds usage guidance. Front-loaded with key verb 'List' and resource 'official FtcRobotController sample OpModes'.

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 listing tool with one optional filter and no output schema, the description is fairly complete. It explains what the tool does and why to use it. Minor missing details about return format, but acceptable given the tool's simplicity.

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 100% (category parameter has a description). The main description adds context by listing example categories (drive code, sensors, etc.), which helps interpret the enum values beyond the schema's 'Filter by sample category'.

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 tool lists official FtcRobotController sample OpModes, provides examples (drive code, sensors, etc.), and distinguishes from sibling tools like get_sample (retrieves a specific sample) and list_opmodes (likely user's own OpModes) by specifying 'official' samples.

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 gives a clear usage hint: 'Start here to find working reference code for any FTC hardware or SDK feature.' This implies use before get_sample or custom code, but lacks explicit when-to-use vs alternatives or when-not-to-use.

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