compile

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It states that compilation occurs, but does not mention side effects such as writing build artifacts, or what output or errors can be expected. As a build operation this is relatively benign, but the absence of any behavioral detail beyond the action itself leaves a clear gap.

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 two clean sentences with no filler. It front-loads the core purpose and immediately gives useful board mappings, so the structure is efficient and easy for an agent to parse.

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 no annotations and no output schema, the description is adequate to convey the command's purpose and required inputs, but it does not describe expected output, failure modes, or prerequisites like installed cores. For a moderately complex tool with six parameters, this is a noticeable but not critical gap.

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%, so the baseline is 3. The description does add a helpful FQBN example (arduino:mbed_portenta:envie_m7) that is not in the schema, but it does not add deeper meaning for sketchPath or the optional parameters, which are already well explained in the schema.

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 uses a specific verb and resource ('Compile a sketch for a board FQBN') and explicitly contrasts with uploading, making the tool's purpose clear and distinguishable from the sibling 'upload' tool. The concrete FQBN examples further reinforce what action is being described.

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?

It clearly states the operation is 'without uploading', giving context that this tool is for compiling rather than flashing, and it provides example board names to indicate target platforms. However, it does not explicitly say when to prefer this tool over alternatives like 'upload' or 'core_install', relying mostly on inference.

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