check_toolchains

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

No annotations are provided, so the description carries the burden. It establishes the read-only, inspection nature of the call and the exact set of toolchains probed, but it does not say whether missing toolchains cause an error or a negative result, whether detection is PATH-based, or whether the call is slow (it may spawn several subprocesses). An output schema exists, so return shape need not be described.

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: the purpose statement is front-loaded, and the enumeration of arduino-cli, pio, idf.py, esptool, openocd, dfu-util, avrdude, and picotool is high-value content rather than filler. Nothing is redundant.

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 parameterless read-only probe with a defined output schema, the description supplies nearly everything an agent needs: what is checked and which binaries count. It stops short of stating failure semantics and how results relate to the related prerequisites/compile tools, so it is not fully complete, but it is adequate for the tool's complexity.

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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly implies no arguments are needed, and the enumerated toolchain list helps the agent interpret what will be reported without adding parameter detail that does not exist.

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 gives a specific verb ('Check availability and versions') and a specific resource ('embedded toolchains on the host machine'), then enumerates the exact binaries inspected. It is clear about scope, but it does not explicitly differentiate itself from the sibling check_prerequisites, which an agent could plausibly pick instead.

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?

Usage is only implied: the word 'Check' and 'on the host machine' suggest a pre-flight diagnostic before compiling or flashing, but no when-to-use condition, prerequisite, or alternative tool is named. The presence of check_prerequisites and run_custom_toolchain among the siblings makes the absence of routing guidance a real gap.

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