compile

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

With no annotations provided, the description carries the full burden. It discloses meaningful behavioral traits: no hardware interaction, read-only semantics, free invocation, and no call limits. It could add more detail about build artifacts or failure behavior, but the core safety-relevant behavior is well covered.

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?

A single compact sentence conveys the action, the return value, the safety profile, and usage freedom. There is no redundant content, and the core facts are front-loaded.

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, optional-parameter compile operation, the description plus schema is largely sufficient. It communicates the output concept ('firmware occupancy') even without an output schema. Minor missing details like output format or compile duration prevent a perfect score.

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 schema already documents both parameters clearly. The description adds no parameter-level meaning beyond what the schema provides, which matches the baseline expectation.

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 states a specific verb ('compiles') and resource ('project'), plus the distinct return value ('firmware occupancy'). It also signals that the tool does not touch hardware, which clearly separates it from sibling tools like flash and erase_flash.

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 clear usage context: it is safe, read-only, free to call, and has no rate limits, so an agent knows when it is appropriate to invoke. It does not explicitly name alternatives for hardware-affecting operations, but the safety framing makes the boundary clear.

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