build_flash_run

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

No annotations provided, so description must carry full burden. It lists three steps and return type, but does not disclose side effects like whether it clears previous builds, requires a connection, or modifies target state. Basic steps are there, but behavioral context is incomplete.

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?

Description is well-structured with a header, numbered steps, and separate sections for args and returns. Every sentence serves a purpose with no redundancy.

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?

Covers purpose, steps, parameter, and return value. Missing details on error conditions or prerequisites (e.g., project must be configured). Given the tool's simplicity, it is nearly complete.

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 coverage is 0%, so description compensates fully. The 'break_at' parameter is explained with its purpose and default value, adding clear meaning beyond the schema's property definition.

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 it performs a full cycle of build, flash, and run to breakpoint, and distinguishes itself as the core 'edit-compile-debug' loop tool. Among siblings like 'build_project' and 'flash_and_run', it uniquely combines all three steps.

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 implies usage for the complete edit-compile-debug cycle and lists the steps, but does not explicitly state when to use alternatives or prerequisites. Clear context but lacks exclusionary guidance.

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