export-binary

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

Annotations already declare readOnly=false, idempotent=true, destructive=false. The description adds useful context that it compiles a sketch and writes firmware artifacts into a folder, but does not disclose build duration, auth/toolchain prerequisites, or whether it overwrites existing files.

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 economical sentences: the action and artifacts come first, followed by the use cases. No filler, front-loaded correctly.

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 build-and-export tool with no output schema, the description adequately conveys what it produces and why an agent would pick it. It omits edge cases such as output collision or failure modes, but is otherwise sufficient for correct invocation.

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 all five parameters are documented in the schema itself. The description only alludes to the folder destination and does not add format or syntax detail beyond the schema, so baseline 3 applies.

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?

Specific compound verb (compile + export) with clear resource (firmware files .hex/.bin/.elf) and destination (a folder). The agent can distinguish this from the sibling 'compile' tool, which builds but does not necessarily emit exportable artifacts.

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?

Gives concrete use contexts: flashing with external tools, OTA updates, archiving builds. However, it does not explicitly contrast with the sibling 'compile' or 'upload' or state when-not to use it, leaving the boundary to inference.

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