stm32_get_target_info

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

With no annotations, the description must carry the behavioral burden. It does disclose that the tool connects to the MCU and reports connection status, and 'retrieves' implies a read operation. But it does not explicitly state that it is non-destructive, whether a debug probe must be attached, or whether it starts its own connection session.

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 compact and front-loaded: the core action appears in the first sentence, followed by a focused bullet list of returned information. There is no filler or redundant phrasing.

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?

The output schema presumably covers return structure, and the description adds useful expected values. However, the definition is incomplete for non-default invocation because it omits parameter semantics, prerequisite conditions, and sibling-tool selection guidance.

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 0%, so the description must compensate for undocumented parameters. It does not mention 'port' or 'freq_khz' at all, leaving the agent without any guidance on how these affect the connection or when to change them.

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 ('retrieves') and resource ('physical STM32 microcontroller'), and lists concrete output fields such as Device ID, core architecture, and flash size. It does not explicitly distinguish itself from siblings like stm32_get_system_status, but the hardware-info focus is clear enough.

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 implied: the agent would call this when it needs target hardware identity or memory size. However, the description never explicitly says when to prefer this over stm32_get_system_status or stm32_list_connected_probes, and gives no exclusions or prerequisites.

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